Re: [PATCH v3 01/10] wildmatch: fix "**" special case
- From
Duy Nguyen <pclouds@gmail.com>
- Date
- Jan 24, 2013, 05:51 UTC
- Message-ID
- <CACsJy8CtV-ngy4iGm3Vn3bu9XwpSrZ_AeWpPxTC2TY_qXv=Cxw@mail.gmail.com>
- In-Reply-To
- <7vwqv3dw2n.fsf@alter.siamese.dyndns.org>
On Thu, Jan 24, 2013 at 11:49 AM, Junio C Hamano <gitster@pobox.com> wrote:
Show 9 quoted lines
>> The only problem I see is, without the version string, there's no way >> to know if "**" is supported. Old git versions will happily take "**" >> and interpret as "*". When you advise someone to use "**" you might >> need to add "check if you have this version of git". This problem does >> not exist with pathspec magic like :(glob) > > OK, so what do we want to do when we do the real "USE_WILDMATCH" > that is not the current experimental curiosity? Use ":(wild)" or > something?
I don't think we need to support two different sets of wildcards in the long run. I'm thinking of adding ":(glob)" with WM_PATHNAME. Pathspec without :(glob) still uses the current wildcards (i.e. no FNM_PATHNAME). At some point, like 2.0, we either switch the behavior of patterns-without-:(glob) to WM_PATHNAME, or just disable wildcards when :(glob) is not present.
-- Duy