Re: [RFC/PATCH] tag: make list exclude !<pattern>
- From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
- Date
- Feb 11, 2012, 14:06 UTC
- Message-ID
- <CACsJy8B3pHZLUuqnmZuqfAo-B=LAm5Q6M4waf4sK8387E9U+uA@mail.gmail.com>
- In-Reply-To
- <m3sjihu18t.fsf@localhost.localdomain>
On Sat, Feb 11, 2012 at 5:13 PM, Jakub Narebski <jnareb@gmail.com> wrote:
Show 8 quoted lines
> Junio C Hamano <gitster@pobox.com> writes: > >> In a future versions, we may want to have "branch/tag --list" also ask for >> FNM_PATHNAME (this *is* a backward incompatible change, so it needs to be >> performed across major version boundary, with backward compatibility >> configurations, deprecation warnings and whole nine yards). Under the new >> match function, today's "branch --list 'maint*'" needs to be spelled as >> "branch --list 'maint*/*'" or something.
One of the reasons I proposed pathspec is to avoid another set of matching syntax in addition to gitattr, gitignore and pathspec, Pathspec magic makes it extensible, FNM_PATHNAME be set that way.
> Or "branch --list 'maint**'
But this comes up a few times already on gitignore discussions. We have fnmatch.c in compat for Windows. Someone just needs to step up and implement "**". It would also a nice thing to add to pathspec syntax, if we can forget the backward compatibility nightmare.
-- Duy