From: Paul Mackerras <paulus@samba.org>
Date: Wed, 08 Feb 2006 02:30:28 GMT
Subject: Re: gitk changing line color for no reason after merge
Message-ID: <17385.22468.218755.833713@cargo.ozlabs.ibm.com>
In-Reply-To: <1139360047.13646.22.camel@dv>

Pavel Roskin writes:

> I'm trying to make it easier to follow a line.  It's easier if its color
> is not changing, especially on trivial nodes (one parent, one child).

OK, you're using "line" to mean something a bit different from the
connection between a commit and its children, which is how I use it.
You seem to be using it more as a "line of development", or as a
series of related patches.  Which is fine, if you can find a way to
identify lines of development automatically.  (I know it looks obvious
when you look at the gitk display, but that's a lot different from
writing down an algorithm to do it.)

> http://red-bean.com/proski/gitk/gitk-ideal.png - made in GIMP.  Trivial
> nodes never change line color, because it changes as soon as the line
> forks.

My problem with that is that it isn't clear that e.g. the green and
brown lines near the bottom actually represent the same parent - and
that will get worse with more complex graphs.

Paul.