Re: How do I...

From: David Woodhouse <dwmw2@infradead.org>
Date: May 6, 2005, 19:10 UTC
Message-ID: <1115406628.16187.353.camel@hades.cambridge.redhat.com>
In-Reply-To: <Pine.LNX.4.58.0505061158520.2233@ppc970.osdl.org>

On Fri, 2005-05-06 at 11:59 -0700, Linus Torvalds wrote:

> I don't do no steenking GUI's. That's for others, and you'll need to
> parse the git-rev-list output yourself to do that.

When I said 'show' I meant merely provide sufficient information.

I believe that what you get at the moment from the command you showed is an unconnected list of commits, each of which may be in different branches, where the _parent_ of each commit you show may not even be included in the list.

I.e. you're giving them a bag of unconnected objects which each look something like this...

		 (COMMIT)--> 
or
		 (COMMIT)--->
		         \-->

But you need to give them a _graph_...

	/------> (COMMIT) --> (COMMIT) --\
 (COMMIT)                                 -> (COMMIT) 
	\-----------> (COMMIT) ----------/

Leaving the pretty GUI as an exercise for the reader is fine. But we do actually have to give enough information to allow them to connect the bits together.

My recursive script attempted this but wasn't quite good enough -- we had enough information to track _merges_ but not _branches_. Hence I was only giving this much information...

	/------> (COMMIT) --> (COMMIT) --\
 (COMMIT)                                 -> (COMMIT) 
	              (COMMIT) ----------/

(...or this one, depending on which order I parsed the tree...)

	         (COMMIT) --> (COMMIT) --\
 (COMMIT)                                 -> (COMMIT) 
	\-----------> (COMMIT) ----------/

-- 
dwmw2