Git development
 help / color / mirror / Atom feed
From: Yuri D'Elia <wavexx@thregr.org>
To: git@vger.kernel.org
Subject: A better git log --graph?
Date: Wed, 07 Jan 2015 15:23:00 +0100	[thread overview]
Message-ID: <m8jfg5$dsp$1@ger.gmane.org> (raw)

Hi everyone,

git log --graph is hard for me to parse mentally when developing a
project which has a lot of branches.

All the tools I've been using seem to just parse log --graph's output,
and thus are no better at showing history.

I would love to have a graph mode where each branch is assigned a
column, and stays there. If my log section shows the history of 3
branches, column 1 should always refer to master, 2 to the hypothetical
"development" branch and 3 to "feature".

Of course the mode will waste more horizontal space, but it would be
immediately more apparent which branch is merging into which.

I saw this idea proposed a couple of times in the mailing list, but I
saw no "action" behind the proposal. Since I don't have time to work on
it, has anyone already started some work that he would like to share as
a starting point? Even just to have a felling if it's worth the effort.

Does anybody know of another tool to graph the history using something
that is not based on git log --graph?

I've seen a couple of graphviz-based ones, but both failed to work out
of the box for me.

Thanks a lot for any pointer.

             reply	other threads:[~2015-01-07 14:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-07 14:23 Yuri D'Elia [this message]
2015-01-07 15:47 ` A better git log --graph? Johan Herland
2015-01-07 16:33   ` Yuri D'Elia
2015-01-07 16:35   ` Junio C Hamano
     [not found] ` <95FA7666-4031-48FE-B9F7-DC8BB969426C@gmail.com>
2015-01-08 11:39   ` Yuri D'Elia
2015-01-08 11:59     ` John Szakmeister

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='m8jfg5$dsp$1@ger.gmane.org' \
    --to=wavexx@thregr.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox