![[tokkee]](http://tokkee.org/images/avatar.png){kind=avatar}
| author | Jens Lehmann <Jens.Lehmann@web.de> | |
| Wed, 28 Oct 2009 11:40:45 +0000 (12:40 +0100) | ||
| committer | Paul Mackerras <paulus@samba.org> | |
| Tue, 3 Nov 2009 11:28:42 +0000 (22:28 +1100) | ||
| commit | 5c838d23aa02476cfe91b0eea047b6d5857da770 | |
| tree | 5aacf98cbdcf9a121e18fbd25f0b1db2140d5ed0 | tree | snapshot |
| parent | 90a77925417646041ac408e591f969d7477be0a9 | commit | diff |
gitk: Use the --submodule option for displaying diffs when available
When displaying diffs in a submodule, this makes gitk display the
headlines of the commits being diffed, instead of just showing
not-quite-helpful SHA-1 pairs, if the underlying git installation
supports this. That makes it much easier to evaluate the changes, as
it eliminates the need to start a gitk inside the submodule and use
the superprojects hashes there to find out what the commits are about.
Since the --submodule option of git diff is new in git version 1.6.6,
this only uses the --submodule option when a git version of 1.6.6 or
higher is detected.
Signed-off-by: Jens Lehmann <Jens.Lehmann@web.de>
Signed-off-by: Paul Mackerras <paulus@samba.org>
When displaying diffs in a submodule, this makes gitk display the
headlines of the commits being diffed, instead of just showing
not-quite-helpful SHA-1 pairs, if the underlying git installation
supports this. That makes it much easier to evaluate the changes, as
it eliminates the need to start a gitk inside the submodule and use
the superprojects hashes there to find out what the commits are about.
Since the --submodule option of git diff is new in git version 1.6.6,
this only uses the --submodule option when a git version of 1.6.6 or
higher is detected.
Signed-off-by: Jens Lehmann <Jens.Lehmann@web.de>
Signed-off-by: Paul Mackerras <paulus@samba.org>
| gitk | diff | blob | history |