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

gitk highlighting descendents/ancestors

From
Paul Mackerras <paulus@samba.org>
Date
May 29, 2006, 12:35 UTC
Message-ID
<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. 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.
Next: Matthias Kestenholz
Message 1 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.