Re: Unresolved issues, "log --graph"

From: Teemu Likonen <tlikonen@iki.fi>
Date: Apr 20, 2008, 15:48 UTC
Message-ID: <20080420154848.GA8647@mithlond.arda.local>
In-Reply-To: <7vbq46fe9h.fsf@gitster.siamese.dyndns.org>

Junio C Hamano wrote (2008-04-19 01:19 -0700):

> Here is an "issues" list I am keeping track of on the back of my head
> (and in "TODO" file on 'todo' branch, which is not updated often
> enough).

> * log --graph (Adam Simpkins)

Hi Adam, any changes for modifying the "log --graph" patch series to make it apply to the current development version of git? It would just feel wrong if this apparently well-designed tool was left behind. Of course it's up to you.

Some thoughts on the graph functionality: I have understood that many Bazaar people like the way "bzr log" indents the log entries which originate from other branches. This way Bazaar users can easily think in terms of commits in the mainline and commits originating from feature branches. I think this is useful distinction sometimes.

I just realised that Adam's "git log --graph" offers the same functionality as "bzr log" but much better. With "git log --graph" user can see the history the way "bzr log" displays it: the current branch is on the leftmost graph line and can be seen as the "mainline" (if wanted); commits coming from other branches are indented and appear in separate graph lines. Yes, there is, and have been, "gitk" of course. "log --graph" is just much closer to "bzr log" view. I think "git log" is quite superiour as it allows many ways of viewing history.