From: Matthias Kestenholz <lists@spinlock.ch>
To: Paul Mackerras <paulus@samba.org>
Cc: git@vger.kernel.org
Subject: Re: gitk highlighting descendents/ancestors
Date: Mon, 29 May 2006 14:55:37 +0200 [thread overview]
Message-ID: <20060529125537.GD4916@spinlock.ch> (raw)
In-Reply-To: <17530.60026.636981.60532@cargo.ozlabs.ibm.com>
Hi,
* Paul Mackerras (paulus@samba.org) wrote:
> I have implemented a feature in gitk (on the "new" branch) where it
> can highlight the commits that are, or are not, descendents or
> ancestors of the selected commit. For now it is invoked via a
> drop-down menu. Does this look useful to people?
>
Yes, this is very useful for me. I have a complicated history graph
because I manage the codebase for several websites with one git
repository. It gets very hard to follow the colored lines in gitk
when there are many merges of feature branches.
The most useful feature for me is probably the "ancestor" view; "not
ancestor" could also be interesting if I wanted to visualize which
feature branches were already merged and which are not.
Thanks,
Matthias
next prev parent reply other threads:[~2006-05-29 12:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-29 12:35 gitk highlighting descendents/ancestors Paul Mackerras
2006-05-29 12:55 ` Matthias Kestenholz [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-24 0:12 Matt Seitz (matseitz)
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=20060529125537.GD4916@spinlock.ch \
--to=lists@spinlock.ch \
--cc=git@vger.kernel.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).