On Tue, Mar 31, 2015 at 6:36 AM, Joey Hess wrote:
> Duy Nguyen wrote:
>> You can do "git --literal-pathspecs ls-files ..." or set
>> GIT_LITERAL_PATHSPECS.
>
> Thanks! --literal-pathspecs does allow getting around this.
>
> Now I'm wondering what other parts of plumbing might be doing globbing
>
On Mon, Mar 30, 2015 at 07:36:14PM -0400, Joey Hess wrote:
> Duy Nguyen wrote:
> > You can do "git --literal-pathspecs ls-files ..." or set
> > GIT_LITERAL_PATHSPECS.
>
> Thanks! --literal-pathspecs does allow getting around this.
>
> Now I'm wondering what other parts of plumbing might be doin
Duy Nguyen wrote:
> You can do "git --literal-pathspecs ls-files ..." or set
> GIT_LITERAL_PATHSPECS.
Thanks! --literal-pathspecs does allow getting around this.
Now I'm wondering what other parts of plumbing might be doing globbing
that I did not anticipate. Maybe I should set the environment v
Hi Joey,
Joey Hess wrote:
> Since I wanted to avoid this wildcard expension, I tried slash-escaping
> the wildcard characters. This works:
>
> joey@darkstar:~/tmp/aaa>git ls-files 'foo\*bar'
> foo*bar
Does 'git --noglob-pathspecs' help?
Curious,
Jonathan
--
To unsubscribe from this list: send t
On Tue, Mar 31, 2015 at 6:04 AM, Joey Hess wrote:
> I was very surprised to learn the other day that git ls-files 'foo*'
> will expand wildcards (including character classes), in the absence of
> expansion by the shell. (git version 2.1.4)
>
> joey@darkstar:~/tmp/aaa>git ls-files 'foo*bar'
> foo*b
I was very surprised to learn the other day that git ls-files 'foo*'
will expand wildcards (including character classes), in the absence of
expansion by the shell. (git version 2.1.4)
joey@darkstar:~/tmp/aaa>git ls-files 'foo*bar'
foo*bar
foobazbar
joey@darkstar:~/tmp/aaa>git ls-files '[abc]'
[abc
6 matches
Mail list logo