From: Junio C Hamano <gitster@pobox.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Tim Friske <me@tifr.de>, git <git@vger.kernel.org>
Subject: Re: Why does "git log -G<regex>" works with "regexp-ignore-case" but not with other regexp-related options?
Date: Tue, 21 Apr 2015 09:59:39 -0700 [thread overview]
Message-ID: <xmqqr3rdific.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <55360D3D.3010201@drmicha.warpmail.net> (Michael J. Gruber's message of "Tue, 21 Apr 2015 10:41:33 +0200")
Michael J Gruber <git@drmicha.warpmail.net> writes:
> We have engine-switching options and engine-modification options. The
> latter are certainly good in the expression itself. Maybe even the
> former, though I don't know how to switch away from fixed-strings in
> that way...
I do not think mixing matching engines in a single request makes
much sense. As the internal machinery is not even prepared to do
that, even though it is prepared to apply engine-modifications ones
to each grep term AFAIK, let's not go there.
next prev parent reply other threads:[~2015-04-21 17:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 10:00 Why does "git log -G<regex>" works with "regexp-ignore-case" but not with other regexp-related options? Tim Friske
2015-04-17 14:26 ` Michael J Gruber
2015-04-17 16:18 ` Junio C Hamano
2015-04-17 17:09 ` Junio C Hamano
2015-04-17 17:45 ` Junio C Hamano
2015-04-20 8:49 ` Michael J Gruber
2015-04-20 17:41 ` Junio C Hamano
2015-04-20 18:33 ` Linus Torvalds
2015-04-20 18:44 ` Junio C Hamano
2015-04-21 8:41 ` Michael J Gruber
2015-04-21 16:59 ` Junio C Hamano [this message]
2015-04-22 9:08 ` Michael J Gruber
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=xmqqr3rdific.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=me@tifr.de \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.