Linus Torvalds writes: > But the real thing I found is that when I decided I wanted to highlight, I > didn't actually want to highlight by "git-rev-list" at all. At least not > most of the time. I just pushed some changes to the "new" branch of the gitk.git repository which change the way we do highlighting. There is now a row of controls across the middle of the window, just below the row containing the sha1 ID, "Find" button, etc., which controls the highlighting. There are (currently) three ways to do highlighting: by path, by view, and by author/committer. The author/committer matching is case-insensitive (since I'm clearly an insensitive sort of guy :) and matches any of the given strings anywhere in the author and committer fields. The path and author/committer entry widgets take a whitespace-delimited list of paths or names of interest, using shell quoting rules, so you can put for example: "david s. miller" benh in there and you'll get commits from either davem or benh highlighted. Do people think this is useful and on the right track interface-wise? Paul. - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html