Re: [PATCH v2 0/7] Tying loose ends on grep-pcre

2012-10-11 Thread Michael Haggerty
On 10/10/2012 06:52 PM, Junio C Hamano wrote: > Michael Haggerty writes: > >>> The last one teaches "git log" family to honor the "grep.*" >>> configuration variables, e.g. "grep.patterntype", so that you can >>> say "git -c grep.patterntype=perl log --grep='(?:pcre)'". >> >> Maybe this has been

Re: [PATCH v2 0/7] Tying loose ends on grep-pcre

2012-10-10 Thread Junio C Hamano
Michael Haggerty writes: >> The last one teaches "git log" family to honor the "grep.*" >> configuration variables, e.g. "grep.patterntype", so that you can >> say "git -c grep.patterntype=perl log --grep='(?:pcre)'". > > Maybe this has been discussed already, but it seems to me that adding a > p

Re: [PATCH v2 0/7] Tying loose ends on grep-pcre

2012-10-10 Thread Michael Haggerty
On 10/10/2012 09:55 AM, Junio C Hamano wrote: > It took longer than expected, but here is a reroll of the previous > series to bring more recent "git grep" enhancements to the "--grep" > option of commands in "git log" family. > > The early part of the series (1-3) refactors the code that reads >

[PATCH v2 0/7] Tying loose ends on grep-pcre

2012-10-10 Thread Junio C Hamano
It took longer than expected, but here is a reroll of the previous series to bring more recent "git grep" enhancements to the "--grep" option of commands in "git log" family. The early part of the series (1-3) refactors the code that reads configuration items related to "grep" and the code that mi