Re: [PATCH v2 05/10] ref-filter: add option to match literal pattern
- From
Karthik Nayak <karthik.188@gmail.com>
- Date
- Jul 11, 2015, 12:54 UTC
- Message-ID
- <CAOLa=ZTvtQrkUqhq5u9h+RfQiqHJmQRAfzZ9KwT5X=-GMuWv+A@mail.gmail.com>
- In-Reply-To
- <vpqvbdryrhh.fsf@anie.imag.fr>
On Sat, Jul 11, 2015 at 2:56 PM, Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> wrote:
Show 28 quoted lines
> Karthik Nayak <karthik.188@gmail.com> writes: > >> On Fri, Jul 10, 2015 at 10:13 PM, Junio C Hamano <gitster@pobox.com> wrote: >>> Karthik Nayak <karthik.188@gmail.com> writes: >>> >>>> Since 'ref-filter' only has an option to match path names >>>> add an option for regular pattern matching. >>> >>> There is nothing "regular" about the pattern matching you are >>> adding. >>> >>> Everywhere else we use patterns on refs we call wildmatch(), which >>> is an enhanced implementation of fnmatch(3), and you are doing the >>> same in this new codepath. >>> >>> Just drop that word from here (and if you said something similar in >>> the documentation, drop "regular" ffrom there as well). It would >>> invite confusion with regular expression matching, which we will not >>> do for refs. >> >> Ok, will do. Thanks > > Just dropping "regular" leads to a strange sentence, since the path name > match is also a kind of pattern-matching. I'd write > > Since 'ref-filter' only has an option to match path names, add an option > for plain fnmatch pattern-matching. >
Thanks for the heads up :)
-- Regards, Karthik Nayak