{"thread":{"id":"4340","subject":"gitk highlighting descendents/ancestors","startedAt":"2006-05-29T12:35:06Z","lastAt":"2006-05-29T12:55:37Z","messageCount":2,"participants":["Paul Mackerras","Matthias Kestenholz"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"20888","messageId":"17530.60026.636981.60532@cargo.ozlabs.ibm.com","threadId":"4340","inReplyTo":null,"subject":"gitk highlighting descendents/ancestors","fromName":"Paul Mackerras","fromEmail":"paulus@samba.org","sentAt":"2006-05-29T12:35:06Z","receivedAt":"2006-05-29T12:35:06Z","isPatch":false,"sender":{"key":"paulus@samba.org","avatar":"https://avatars.githubusercontent.com/u/1606439?v=4"},"body":"I have implemented a feature in gitk (on the \"new\" branch) where it\ncan highlight the commits that are, or are not, descendents or\nancestors of the selected commit.  For now it is invoked via a\ndrop-down menu.  Does this look useful to people?\n\nAt the moment, if you select \"Not descendent\" then the selected\ncommit and all the commits below it will be highlighted (since they\ncan't be descendents of the selected commit).  Similarly if you select\n\"Not ancestor\" then the selected commit and all commits above it are\nhighlighted.  That's technically correct but doesn't seem very useful;\nmaybe I should suppress those highlights.\n\nAlso, whatever matches the string put in the \"Find\" field will be\nhighlighted.  I have taken out the \"Files\" and \"Pickaxe\" options in\nthe Find function, and put the pickaxe function into a new drop-down\nmenu for the highlighting function.  I have code ready to go for\nshift-up and shift-down to move to the previous/next highlighted row,\nonce Junio applies my tiny patch to builtin-diff-tree.c.\n\nPaul.\n"},{"id":"20889","messageId":"20060529125537.GD4916@spinlock.ch","threadId":"4340","inReplyTo":"17530.60026.636981.60532@cargo.ozlabs.ibm.com","subject":"Re: gitk highlighting descendents/ancestors","fromName":"Matthias Kestenholz","fromEmail":"lists@spinlock.ch","sentAt":"2006-05-29T12:55:37Z","receivedAt":"2006-05-29T12:55:37Z","isPatch":false,"sender":{"key":"lists@spinlock.ch","avatar":null},"body":"Hi,\n\n* Paul Mackerras (paulus@samba.org) wrote:\n> I have implemented a feature in gitk (on the \"new\" branch) where it\n> can highlight the commits that are, or are not, descendents or\n> ancestors of the selected commit.  For now it is invoked via a\n> drop-down menu.  Does this look useful to people?\n> \n\nYes, this is very useful for me. I have a complicated history graph\nbecause I manage the codebase for several websites with one git\nrepository. It gets very hard to follow the colored lines in gitk\nwhen there are many merges of feature branches.\n\nThe most useful feature for me is probably the \"ancestor\" view; \"not\nancestor\" could also be interesting if I wanted to visualize which\nfeature branches were already merged and which are not.\n\nThanks,\nMatthias\n"}]}