Re: What's cooking in git.git (Oct 2012, #06; Fri, 19)

From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date: Oct 21, 2012, 04:24 UTC
Message-ID: <CACsJy8A2PdG69hB1=YgHMAdibO=7_Uu5qvmyAqcrhdBVWy761g@mail.gmail.com>
In-Reply-To: <7vmwzii37w.fsf@alter.siamese.dyndns.org>

On Sat, Oct 20, 2012 at 4:03 AM, Junio C Hamano <gitster@pobox.com> wrote:

Show 10 quoted lines

> * nd/wildmatch (2012-10-15) 13 commits
>
>  Allows pathname patterns in .gitignore and .gitattributes files
>  with double-asterisks "foo/**/bar" to match any number of directory
>  hierarchies.
>
>  I suspect that this needs to be plugged to pathspec matching code;
>  otherwise "git log -- 'Docum*/**/*.txt'" would not show the log for
>  commits that touch Documentation/git.txt, which would be confusing
>  to the users.

I do want non-recursive "*" in pathspec and "**" can help retain the recursive "*" semantics. But can we just flip the coin at some point and change "*" semantics in pathspec from recursive to non-recursive?

I have no problem with that but then we might want to change other places that use fnmatch without FNM_PATHNAME too, e.g. apply, branch, for-each-ref... Or we could go with new syntax ":(glob)Docu*/**/*.txt". A bit ugly.

-- 
Duy