From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Bart Trojanowski <bart@jukie.net>, git@vger.kernel.org
Subject: Re: [PATCH] Add git-rev-list --invert-match
Date: Thu, 20 Sep 2007 22:54:46 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0709202252570.28395@racer.site> (raw)
In-Reply-To: <7vtzppj9d1.fsf@gitster.siamese.dyndns.org>
Hi,
On Thu, 20 Sep 2007, Junio C Hamano wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > 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."
>
> Yeah. And I think we would also want to have that at the
> underlying "grep" layer wouldn't we?
That's what I tried to get at... Already on IRC, I tried to direct the
attention to that thread on the list... There I had an ugly patch, which
was incomplete, mainly because I did not sort out the semantics first.
But the idea was to put this into grep.c so that both git-log and git-grep
could benefit from that feature.
Ciao,
Dscho
next prev parent reply other threads:[~2007-09-20 21:55 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
2007-09-20 21:49 ` Junio C Hamano
2007-09-20 21:54 ` Johannes Schindelin [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* 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.0709202252570.28395@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=bart@jukie.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).