From: Peter Baumann <peter.baumann@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: git@vger.kernel.org
Subject: Re: Any objectsions to enhancing git-log to show tags/branch heads?
Date: Mon, 16 Apr 2007 20:13:52 +0200 [thread overview]
Message-ID: <20070416181352.GB29569@xp.machine.xx> (raw)
In-Reply-To: <E1HdQah-0008Q2-7E@candygram.thunk.org>
On Mon, Apr 16, 2007 at 08:45:55AM -0400, Theodore Ts'o wrote:
>
> 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@mit.edu>
> 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@woody.linux-foundation.org>
> 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
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 /
|
tig comes near it, but it only linerarises the branches, so you can't see
where there was a mergepoint/fork. I'd really like these visuallization of
the commit graph in some of the text viewers. I normally don't care about
the _full_ commit text, only if I visually understand what's happening I'm
looking at the individual commits and the patches.
There was some tool (can't remember its name or who it wrote; but posted
here on this list) which visualizes the relation horizontaly and not
vertically as shown above but has a limit of only displaying around 25 (not
sure about this number; but definitly below 30 commits) which was at least
displaying the commit graph which is _really_ really what I need.
-Peter
next prev parent reply other threads:[~2007-04-16 18:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-16 12:45 Any objectsions to enhancing git-log to show tags/branch heads? Theodore Ts'o
2007-04-16 17:46 ` Junio C Hamano
2007-04-16 20:46 ` Theodore Tso
2007-04-16 18:13 ` Peter Baumann [this message]
2007-04-16 18:27 ` J. Bruce Fields
2007-04-17 5:07 ` Peter Baumann
2007-04-17 13:36 ` J. Bruce Fields
2007-04-16 19:01 ` Julian Phillips
2007-04-17 5:08 ` Peter Baumann
2007-04-16 23:00 ` Linus Torvalds
2007-04-17 2:21 ` Theodore Tso
2007-04-17 2:30 ` Jakub Narebski
2007-04-17 3:00 ` Linus Torvalds
2007-04-23 10:00 ` Junio C Hamano
2007-04-17 3:15 ` Theodore Tso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070416181352.GB29569@xp.machine.xx \
--to=peter.baumann@gmail.com \
--cc=git@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).