Junio C Hamano venit, vidit, dixit 21.04.2015 18:59:
Michael J Gruber g...@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
Junio C Hamano venit, vidit, dixit 20.04.2015 20:44:
Linus Torvalds torva...@linux-foundation.org writes:
And to clarify: I don't suggest always building with libpcre. I
literally suggest having something like
/* hacky mac-hack hack */
if (strncmp((?i), p-pattern, 4)) {
Michael J Gruber g...@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
Junio C Hamano venit, vidit, dixit 17.04.2015 19:45:
On Fri, Apr 17, 2015 at 7:26 AM, Michael J Gruber
g...@drmicha.warpmail.net wrote:
Similarly I think it is not very consistent that one cannot combine any of
the above options with the Sstring but instead have yet another option
called
Michael J Gruber g...@drmicha.warpmail.net writes:
They [jc: -S and -G] have different semantics, and *therefore*
they have different defaults, and *therefore* a user may want to
switch one of them (or --grep or --author or...) to
--fixed--strings and keep the other to --regexp.
Ahh, OK.
Linus Torvalds torva...@linux-foundation.org writes:
And to clarify: I don't suggest always building with libpcre. I
literally suggest having something like
/* hacky mac-hack hack */
if (strncmp((?i), p-pattern, 4)) {
p-pattern += 4;
p-ignore_case = true;
}
On Mon, Apr 20, 2015 at 10:41 AM, Junio C Hamano gits...@pobox.com wrote:
Ahh, OK. And not just -S and -G, the fields in headers may be
something user may want to switch independently?
So personally, I hate extra command line flags for this. I'd much
rather see is use something in the regular
Hi,
I wonder why git log -Gregexp works with the regexp-ignore-case
option but not with the other regexp-related options? Wouldn't it be
useful to make the Gregex option support the following options?
* basic-regexp
* extended-regexp
* fixed-strings
* perl-regexp
Similarly I think it
Tim Friske venit, vidit, dixit 17.04.2015 12:00:
Hi,
I wonder why git log -Gregexp works with the regexp-ignore-case
option but not with the other regexp-related options? Wouldn't it be
useful to make the Gregex option support the following options?
* basic-regexp
* extended-regexp
Michael J Gruber g...@drmicha.warpmail.net writes:
Similarly I think it is not very consistent that one cannot combine any of
the above options with the Sstring but instead have yet another option
called pickaxe-regex to toggle between fixed-string and
extended-regexp semantics for the
Michael J Gruber g...@drmicha.warpmail.net writes:
Similarly I think it is not very consistent that one cannot combine any of
the above options with the Sstring but instead have yet another option
called pickaxe-regex to toggle between fixed-string and
extended-regexp semantics for the
On Fri, Apr 17, 2015 at 7:26 AM, Michael J Gruber
g...@drmicha.warpmail.net wrote:
Similarly I think it is not very consistent that one cannot combine any of
the above options with the Sstring but instead have yet another option
called pickaxe-regex to toggle between fixed-string and
12 matches
Mail list logo
