Re: Any objectsions to enhancing git-log to show tags/branch heads?
- From
- Peter Baumann <peter.baumann@gmail.com>
- Date
- Apr 17, 2007, 05:07 UTC
- Message-ID
- <20070417050704.GA19925@xp.machine.xx>
- In-Reply-To
- <20070416182749.GG23764@fieldses.org>
On Mon, Apr 16, 2007 at 02:27:49PM -0400, J. Bruce Fields wrote:
Show 19 quoted lines
> On Mon, Apr 16, 2007 at 08:13:52PM +0200, Peter Baumann wrote: > > I'll do this gitk jump very often, too. Just to get the big picture where my > > branches are (inside the commit graph). As they stay normaly on the tip, I > > exit gitk long before it reached the root commit. What I'd like to have is > > something which shows me _visually_ the the branches, e.g. > > > > master > > | next commit comment for next > > o | commit comment for master~1 > > | o commit comment for next~1 > > o | [ ... guess whats next :-) you get the idea ...] > > | o > > | | > > o / > > | > > git show-branch? > > --b.
No. git-show-branch produces output like the snippet below, which is totally non obious to me. Yes, I could figure out what it means, but why the hell _should_ I if there are tools for which you have to look just for a second on the ouput to _fully_ understand whats happening?
-Peter
xp:~/src/git (master)$ git show-branch ! [editpatch] Merge branch 'maint' * [master] Merge branch 'jc/index-output' ! [pu] Merge branch 'jc/diff' into pu --- - [master] Merge branch 'jc/index-output' * [master^2] git-read-tree --index-output=<file> * [master^2^] _GIT_INDEX_OUTPUT: allow plumbing to output to an alternative index file. * [master^^2] Makefile: Add '+' to QUIET_SUBDIR0 to fix parallel make. * [master~2^2] git-bisect: allow bisecting with only one bad commit. * [master~2^2^] t6030: add a bit more tests to git-bisect * [master~2^2~2] git-bisect: moderni ...