I've recently noticed that I'm often firing up gitk for no other purpose
than to see which changesets have which tags and branch heads. Often
I'll fire up gitk, quickly look at the tags/branches, and then kill it
before it's done parsing the repository, resulting in python errors as
it dies.
So I'm wondering why we haven't arranged to have git-log show this
information, and whether there would be any objections if "git-log"
showed something like this:
commit 7d5021d2ef5d414908d8e4db26c324c1de19f9f1
Head: tytso-patches-20070223
Author: Theodore Ts'o <tytso@xxxxxxx>
Date: Fri Feb 23 14:46:01 2007 -0500
Cherry pick "unload head on shutdown" patch
...
commit c8f71b01a50597e298dc3214a2f2be7b8d31170c
Tag: v2.6.21-rc1
Author: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Tue Feb 20 20:32:30 2007 -0800
Linux 2.6.21-rc1
Would there be objections in adding this to --pretty=medium (i.e., the
default), or would it be better to add something like tihs to
--pretty=full or --pretty=fuller?
The only reason why I could imagine not doing this by default would be a
potential performance problem if there were thousands of heads or branch
heads.
- Ted
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html