On Mon, Sep 22, 2014 at 8:24 AM, Duy Nguyen wrote:
> On Mon, Sep 22, 2014 at 2:52 AM, Torsten Bögershausen wrote:
>> git status takes a "pathspec" as a parameter, which is not the same as a
>> filename.
>> A pathspec can contain wildcards like '*' or '?' or things like "*[ch]".
>> This is known
On Mon, Sep 22, 2014 at 2:52 AM, Torsten Bögershausen wrote:
> git status takes a "pathspec" as a parameter, which is not the same as a
> filename.
> A pathspec can contain wildcards like '*' or '?' or things like "*[ch]".
> This is known as shell glob syntax (or so), and used automatically by al
On 2014-09-21 20.04, Rémi Vanicat wrote:
> Hello,
>
> I found what look like a bug in git status:
> `git status -unormal foo[b]/` won't output the content of the directory
> foo[b] when `git status -unormal foo/` will output the content of the
> directory foo:
>
> $ mkdir 'foo[b]'
> $ touch
Hello,
I found what look like a bug in git status:
`git status -unormal foo[b]/` won't output the content of the directory
foo[b] when `git status -unormal foo/` will output the content of the
directory foo:
$ mkdir 'foo[b]'
$ touch 'foo[b]/bar'
$ git status -unormal 'foo[b]/'
On branch
4 matches
Mail list logo
