Re: git stash push -u always warns "pathspec '...' did not match any files"

2018-03-10 Thread Thomas Gummerer
On 03/10, Marc Strapetz wrote: > On 09.03.2018 23:18, Junio C Hamano wrote: > >Marc Strapetz writes: > > > >>Thanks, I can confirm that the misleading warning message is fixed. > >> > >>What I've noticed now is that when using -u option, Git won't warn if > >>the

Re: git stash push -u always warns "pathspec '...' did not match any files"

2018-03-10 Thread Marc Strapetz
On 09.03.2018 23:18, Junio C Hamano wrote: Marc Strapetz writes: Thanks, I can confirm that the misleading warning message is fixed. What I've noticed now is that when using -u option, Git won't warn if the pathspec is actually not matching a file. Also, an empty

Re: git stash push -u always warns "pathspec '...' did not match any files"

2018-03-09 Thread Junio C Hamano
Marc Strapetz writes: > Thanks, I can confirm that the misleading warning message is fixed. > > What I've noticed now is that when using -u option, Git won't warn if > the pathspec is actually not matching a file. Also, an empty stash may > be created. S..., does

Re: git stash push -u always warns "pathspec '...' did not match any files"

2018-03-04 Thread Marc Strapetz
On 03.03.2018 16:46, Thomas Gummerer wrote: On 03/03, Marc Strapetz wrote: Reproducible in a test repository with following steps: $ touch untracked $ git stash push -u -- untracked Saved working directory and index state WIP on master: 0096475 init fatal: pathspec 'untracked' did not match

Re: git stash push -u always warns "pathspec '...' did not match any files"

2018-03-03 Thread Thomas Gummerer
On 03/03, Marc Strapetz wrote: > Reproducible in a test repository with following steps: > > $ touch untracked > $ git stash push -u -- untracked > Saved working directory and index state WIP on master: 0096475 init > fatal: pathspec 'untracked' did not match any files > error: unrecognized input