* gitk highlighting descendents/ancestors
@ 2006-05-29 12:35 Paul Mackerras
2006-05-29 12:55 ` Matthias Kestenholz
0 siblings, 1 reply; 3+ messages in thread
From: Paul Mackerras @ 2006-05-29 12:35 UTC (permalink / raw)
To: git
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?
At the moment, if you select "Not descendent" then the selected
commit and all the commits below it will be highlighted (since they
can't be descendents of the selected commit). Similarly if you select
"Not ancestor" then the selected commit and all commits above it are
highlighted. That's technically correct but doesn't seem very useful;
maybe I should suppress those highlights.
Also, whatever matches the string put in the "Find" field will be
highlighted. I have taken out the "Files" and "Pickaxe" options in
the Find function, and put the pickaxe function into a new drop-down
menu for the highlighting function. I have code ready to go for
shift-up and shift-down to move to the previous/next highlighted row,
once Junio applies my tiny patch to builtin-diff-tree.c.
Paul.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: gitk highlighting descendents/ancestors
2006-05-29 12:35 gitk highlighting descendents/ancestors Paul Mackerras
@ 2006-05-29 12:55 ` Matthias Kestenholz
0 siblings, 0 replies; 3+ messages in thread
From: Matthias Kestenholz @ 2006-05-29 12:55 UTC (permalink / raw)
To: Paul Mackerras; +Cc: git
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: gitk highlighting descendents/ancestors
@ 2008-07-24 0:12 Matt Seitz (matseitz)
0 siblings, 0 replies; 3+ messages in thread
From: Matt Seitz (matseitz) @ 2008-07-24 0:12 UTC (permalink / raw)
To: git
"Paul Mackerras" <paulus@samba.org> wrote in message news:<17530.60026.636981.60532@cargo.ozlabs.ibm.com>...
> 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.
Is this feature still available? I don't see the menu running 1.5.6 on Cygwin. A coworker running 1.5.0.7 on Linux sees it.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-07-24 0:12 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-05-29 12:35 gitk highlighting descendents/ancestors Paul Mackerras
2006-05-29 12:55 ` Matthias Kestenholz
-- strict thread matches above, loose matches on Subject: below --
2008-07-24 0:12 Matt Seitz (matseitz)
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).