From: Paul Mackerras <paulus@samba.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: gitk highlight feature
Date: Sat, 20 May 2006 10:07:28 +1000 [thread overview]
Message-ID: <17518.24000.952384.563448@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0605030946260.4086@g5.osdl.org>
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.
next prev parent reply other threads:[~2006-05-20 0:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 23:44 gitk highlight feature Paul Mackerras
2006-05-02 23:48 ` Junio C Hamano
2006-05-03 0:17 ` Paul Mackerras
2006-05-03 0:07 ` Linus Torvalds
2006-05-03 0:23 ` Linus Torvalds
2006-05-03 2:55 ` Paul Mackerras
2006-05-03 16:57 ` Linus Torvalds
2006-05-03 23:08 ` Paul Mackerras
2006-05-03 23:25 ` Linus Torvalds
2006-05-20 0:07 ` Paul Mackerras [this message]
2006-05-20 16:42 ` Linus Torvalds
2006-05-21 0:40 ` Paul Mackerras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17518.24000.952384.563448@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).