author | Jens Lehmann <Jens.Lehmann@web.de> | |
Sat, 16 Jan 2010 17:42:24 +0000 (18:42 +0100) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Sun, 17 Jan 2010 00:40:50 +0000 (16:40 -0800) | ||
commit | ee6fc514f2df821c2719cc49499a56ef2fb136b0 | |
tree | f5aa79026dcad4897fbb0501027d70a5d8a48cd1 | tree | snapshot |
parent | 1f73566af5bec28cd8489c6139a9ede95817349c | commit | diff |
Show submodules as modified when they contain a dirty work tree
Until now a submodule only then showed up as modified in the supermodule
when the last commit in the submodule differed from the one in the index
or the diffed against commit of the superproject. A dirty work tree
containing new untracked or modified files in a submodule was
undetectable when looking at it from the superproject.
Now git status and git diff (against the work tree) in the superproject
will also display submodules as modified when they contain untracked or
modified files, even if the compared ref matches the HEAD of the
submodule.
Signed-off-by: Jens Lehmann <Jens.Lehmann@web.de>
Signed-off-by: Nanako Shiraishi <nanako3@lavabit.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Until now a submodule only then showed up as modified in the supermodule
when the last commit in the submodule differed from the one in the index
or the diffed against commit of the superproject. A dirty work tree
containing new untracked or modified files in a submodule was
undetectable when looking at it from the superproject.
Now git status and git diff (against the work tree) in the superproject
will also display submodules as modified when they contain untracked or
modified files, even if the compared ref matches the HEAD of the
submodule.
Signed-off-by: Jens Lehmann <Jens.Lehmann@web.de>
Signed-off-by: Nanako Shiraishi <nanako3@lavabit.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
diff-lib.c | diff | blob | history | |
submodule.c | diff | blob | history | |
submodule.h | diff | blob | history | |
t/t7506-status-submodule.sh | diff | blob | history |