| commit | 18076502cb282482f3cd75d766e1478cc3fccc29 | |
| author | Jens Lehmann <Jens.Lehmann@web.de> | |
| Fri, 25 Jun 2010 14:56:02 +0000 (25 16:56 +0200) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Fri, 25 Jun 2010 18:12:27 +0000 (25 11:12 -0700) | ||
| tree | 943b0b388d7d8eb89876d94c196d6423bc355ae3 | treesnapshot (tar.gz zip) |
| parent | 6ed7ddaadba9217b794aecf6d74a2e455daf7a96 | commitdiff |
git submodule: ignore dirty submodules for summary and status
The summary and status commands only care about submodule commits, so it is
rather pointless that they check for dirty work trees. This saves the time
needed to scan the submodules work tree. Even "git status" profits from these
savings when the status.submodulesummary config option is set, as this lead to
traversing the submodule work trees twice, once for status and once again for
the submodule summary. And if the submodule was just dirty, submodule summary
produced rather meaningless output anyway:
* sub 1234567...1234567 (0):
Signed-off-by: Jens Lehmann <Jens.Lehmann@web.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
The summary and status commands only care about submodule commits, so it is
rather pointless that they check for dirty work trees. This saves the time
needed to scan the submodules work tree. Even "git status" profits from these
savings when the status.submodulesummary config option is set, as this lead to
traversing the submodule work trees twice, once for status and once again for
the submodule summary. And if the submodule was just dirty, submodule summary
produced rather meaningless output anyway:
* sub 1234567...1234567 (0):
Signed-off-by: Jens Lehmann <Jens.Lehmann@web.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| git-submodule.sh | diffblobblamehistory |