All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: git@vger.kernel.org
Subject: Re: Any objectsions to enhancing git-log to show tags/branch heads?
Date: Tue, 17 Apr 2007 09:36:52 -0400	[thread overview]
Message-ID: <20070417133652.GC11907@fieldses.org> (raw)
In-Reply-To: <20070417050704.GA19925@xp.machine.xx>

On Tue, Apr 17, 2007 at 07:07:04AM +0200, Peter Baumann wrote:
> On Mon, Apr 16, 2007 at 02:27:49PM -0400, J. Bruce Fields wrote:
> > 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?

Yeah, I find it pretty opaque too.--b.

  reply	other threads:[~2007-04-17 13:36 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 [this message]
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=20070417133652.GC11907@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=git@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.