git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: gitk highlighting descendents/ancestors

From
MKMatthias Kestenholz <lists@spinlock.ch>
Date
May 29, 2006, 12:55 UTC
Message-ID
<20060529125537.GD4916@spinlock.ch>
In-Reply-To
<17530.60026.636981.60532@cargo.ozlabs.ibm.com>
Hi,
* Paul Mackerras (paulus@samba.org) wrote:
Show 5 quoted lines
> 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

Previous: Paul Mackerras
Message 2 of 2 in “gitk highlighting descendents/ancestors”
  1. Paul MackerrasMay 29, 2006
  2. Matthias KestenholzMay 29, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.