From: Junio C Hamano <gitster@pobox•com>
To: Paul Mackerras <paulus@samba•org>
Cc: git@vger•kernel.org, Christoph Junghans <ottxor@gentoo•org>
Subject: [PATCH] gitk: pass --invert-grep option down to "git log"
Date: Sun, 15 Feb 2015 23:29:10 -0800 [thread overview]
Message-ID: <xmqqd25a71rt.fsf_-_@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1421112812-13578-1-git-send-email-ottxor@gentoo.org> (Christoph Junghans's message of "Mon, 12 Jan 2015 18:33:32 -0700")
From: Christoph Junghans <ottxor@gentoo•org>
Date: Mon, 12 Jan 2015 18:33:32 -0700
"git log --grep=<string>" shows only commits with messages that
match the given string, but sometimes it is useful to be able to
show only commits that do *not* have certain messages (e.g. "show
me ones that are not FIXUP commits").
Now the underlying "git log" learned the "--invert-grep" option.
The option syntactically behaves similar to "--all-match" that
requires that all of the grep strings to match and semantically
behaves the opposite---it requires that none of the grep strings to
match.
Teach "gitk" to allow users to pass it down to underlying "git log"
command by adding it to the known_view_options array.
Signed-off-by: Christoph Junghans <ottxor@gentoo•org>
Signed-off-by: Junio C Hamano <gitster@pobox•com>
---
* Split from Christoph's original patch ($gmane/262313).
gitk | 1 +
1 file changed, 1 insertion(+)
diff --git b/gitk a/gitk
index 3520bda..a95a93f 100755
--- b/gitk
+++ a/gitk
@@ -4036,6 +4036,7 @@ set known_view_options {
{committer t15 . "--committer=*" {mc "Committer:"}}
{loginfo t15 .. "--grep=*" {mc "Commit Message:"}}
{allmatch b .. "--all-match" {mc "Matches all Commit Info criteria"}}
+ {igrep b .. "--invert-grep" {mc "Matches none Commit Info criteria"}}
{changes_l l + {} {mc "Changes to Files:"}}
{pickaxe_s r0 . {} {mc "Fixed String"}}
{pickaxe_t r1 . "--pickaxe-regex" {mc "Regular Expression"}}
next prev parent reply other threads:[~2015-02-16 7:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 2:14 [PATCH] git-log: added --invert-grep option Christoph Junghans
2014-12-19 6:50 ` Junio C Hamano
2014-12-24 3:03 ` Christoph Junghans
2014-12-24 3:03 ` [PATCH] git-log: added --grep-begin .. --grep-end syntax Christoph Junghans
2014-12-29 17:56 ` [PATCH] git-log: added --invert-grep option Junio C Hamano
2015-01-04 5:27 ` [PATCH] git-log: added --none-match option Christoph Junghans
2015-01-06 23:02 ` Junio C Hamano
2015-01-09 22:33 ` Christoph Junghans
2015-01-09 22:55 ` Junio C Hamano
2015-01-12 20:51 ` Junio C Hamano
2015-01-12 1:39 ` [PATCH v2] " Christoph Junghans
2015-01-13 1:33 ` [PATCH v2] log: teach --invert-grep option Christoph Junghans
2015-01-13 18:25 ` Junio C Hamano
2015-02-16 7:29 ` Junio C Hamano [this message]
2015-03-22 3:39 ` [PATCH] gitk: pass --invert-grep option down to "git log" 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=xmqqd25a71rt.fsf_-_@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=ottxor@gentoo$(echo .)org \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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