author | Jim Meyering <jim@meyering.net> | |
Sat, 10 Dec 2011 15:08:57 +0000 (16:08 +0100) | ||
committer | Paul Mackerras <paulus@samba.org> | |
Sun, 18 Mar 2012 23:16:53 +0000 (10:16 +1100) | ||
commit | 6c9e2d1842c8ab6e283df8633b42254fc1e2fcc6 | |
tree | f45748d33d4db762d7a086a9cb8468e4f8aeab65 | tree | snapshot |
parent | 65bb0bda75f4070a609d266d7231b4ec53d56972 | commit | diff |
gitk: Make "git describe" output clickable, too
Automake's contribution guidelines suggest using "git describe" output
in commit logs to reference previous commits. By contrast, in
coreutils, I had acquired the habit of using a bare SHA1 prefix (8 hex
digits), since gitk creates clickable links for that, and not for "git
describe" output.
I prefer the readability of the full "git describe" output, yet want
to retain the gitk links, so this renders as clickable not just
SHA1-like strings, but also an SHA1-like string that is prefixed by
"-g".
Signed-off-by: Jim Meyering <meyering@redhat.com>
Signed-off-by: Paul Mackerras <paulus@samba.org>
Automake's contribution guidelines suggest using "git describe" output
in commit logs to reference previous commits. By contrast, in
coreutils, I had acquired the habit of using a bare SHA1 prefix (8 hex
digits), since gitk creates clickable links for that, and not for "git
describe" output.
I prefer the readability of the full "git describe" output, yet want
to retain the gitk links, so this renders as clickable not just
SHA1-like strings, but also an SHA1-like string that is prefixed by
"-g".
Signed-off-by: Jim Meyering <meyering@redhat.com>
Signed-off-by: Paul Mackerras <paulus@samba.org>
gitk | diff | blob | history |