From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Bart Trojanowski <bart@jukie.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Add git-rev-list --invert-match
Date: Thu, 20 Sep 2007 14:12:54 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0709201403540.28395@racer.site> (raw)
In-Reply-To: <20070920123849.GD12076@jukie.net>
Hi,
On Thu, 20 Sep 2007, Bart Trojanowski wrote:
> * Johannes Schindelin <Johannes.Schindelin@gmx.de> [070920 06:34]:
> > On Wed, 19 Sep 2007, Bart Trojanowski wrote:
> > > git log --invert-match --grep="uninteresting"
> >
> > IMHO this is only half a solution. Some of us want to say "git log
> > --grep=this --but-not-(in-the-whole-message) --grep=that".
>
> I have noticed that unique negation flags are getting scarce... we
> already have --reverse, --inverse, and --not mean something elsewhere.
> --but-not maybe be good.
>
> I also agree that git-grep could use this extension.
>
> Anyways, I can see four solutions for adding "show me this but not that"
> functionality to git-rev-list:
>
> 1) adding a --but-not flag, as you suggested. It separates positive
> matches that precede it with negative matches that follow.
>
> Example:
> git log --grep=this --but-not --grep=that --committer="${MY_EMAIL}"
That is basically the approach taken by
http://article.gmane.org/gmane.comp.version-control.git/51874
(Yes, since you refused to search in the mailing list archives, I did it
for you... this time!)
> 2) Adding --not-grep, --not-author, --not-committer which add negative
> matches. Maybe even --grep!=PATTERN, --author!=PATTERN, ...
>
> Example:
> git log --grep=this --not-grep=that --committer!="${MY_EMAIL}"
That sounds sensible.
> 3) Extending the PATTERN we accept in --grep, --author, and --committer,
> such that a prefix in the pattern tells us how to use the match:
> --grep=!PATTERN
>
> Example:
> git log --grep=this --grep='!that' --committer="!${MY_EMAIL}"
Now you can no longer avoid defining clean semantics: what does that mean?
Does it mean that there is _one_ line that does not have "that" in it, or
is it the complete message?
Further, it probably makes sense to have the option to say _both_: "Find
me a commit that contains Bart in one line, but not Simpson, and that
does not contain the word "Sverdoolaege" at all."
> 4) (going on a limb here) Can this kind of match be done with perl
> regular expressions? Maybe we could use --perl-regexp
>
> Example:
> I've got nothing :)
This time you'll have to find the thread yourself. Hint: search for pcre.
Ciao,
Dscho
next prev parent reply other threads:[~2007-09-20 13:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 20:26 [PATCH] Add git-rev-list --invert-match Bart Trojanowski
2007-09-20 2:52 ` Bart Trojanowski
2007-09-20 4:05 ` Junio C Hamano
2007-09-20 12:18 ` Bart Trojanowski
2007-09-20 10:32 ` Johannes Schindelin
2007-09-20 12:38 ` Bart Trojanowski
2007-09-20 13:12 ` Johannes Schindelin [this message]
2007-09-20 21:49 ` Junio C Hamano
2007-09-20 21:54 ` Johannes Schindelin
2007-09-22 1:38 ` [RFC] Add git-rev-list --not-(author|committer|grep)!=pattern Bart Trojanowski
2007-09-21 4:18 ` [PATCH] Add git-rev-list --invert-match Jeff King
2007-09-21 9:10 ` Johannes Schindelin
2007-09-21 9:19 ` Jeff King
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=Pine.LNX.4.64.0709201403540.28395@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=bart@jukie.net \
--cc=git@vger.kernel.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).