Marc Strapetz <marc.strapetz@xxxxxxxxxxx> 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. Soooo..., does it mean that the patch Thomas posted and you confirmed trades one issue with another issue with a similar graveness? Is this something we want to "fix" without adding another breakage?
