From: Peter Baumann <waste.manager@gmx.de>
To: git@vger.kernel.org
Cc: Julian Phillips <julian@quantumfyre.co.uk>
Subject: Re: Any objectsions to enhancing git-log to show tags/branch heads?
Date: Tue, 17 Apr 2007 07:08:08 +0200 [thread overview]
Message-ID: <20070417050808.GC29569@xp.machine.xx> (raw)
In-Reply-To: <Pine.LNX.4.64.0704161958470.6021@reaper.quantumfyre.co.uk>
On Mon, Apr 16, 2007 at 08:01:29PM +0100, Julian Phillips wrote:
> On Mon, 16 Apr 2007, Peter Baumann wrote:
>
> >
> > 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.
>
> If you turn on the revision graph visualisation (press 'g' whil in main
> view) then tig will show merges and forks ... looks a little like your
> diagram above in fact.
>
> --
> Julian
>
Nice. I didn't now of this feature.
Peter
next prev parent reply other threads:[~2007-04-17 5:14 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
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 [this message]
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=20070417050808.GC29569@xp.machine.xx \
--to=waste.manager@gmx.de \
--cc=git@vger.kernel.org \
--cc=julian@quantumfyre.co.uk \
/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).