From: Paul Mackerras <paulus@samba.org>
To: Pavel Roskin <proski@gnu.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: gitk changing line color for no reason after merge
Date: Wed, 8 Feb 2006 13:30:28 +1100 [thread overview]
Message-ID: <17385.22468.218755.833713@cargo.ozlabs.ibm.com> (raw)
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.
next prev parent reply other threads:[~2006-02-08 2:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 17:21 gitk changing line color for no reason after merge Pavel Roskin
2006-02-07 5:18 ` Pavel Roskin
2006-02-07 8:56 ` Paul Mackerras
2006-02-08 1:10 ` Pavel Roskin
2006-02-07 10:04 ` Junio C Hamano
2006-02-08 0:54 ` Pavel Roskin
2006-02-08 2:30 ` Paul Mackerras [this message]
2006-02-08 21:06 ` Pavel Roskin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17385.22468.218755.833713@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=proski@gnu.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).