On 09.03.2018 23:18, Junio C Hamano wrote:
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?
From my understanding these are two separate problems for which the new
one was somewhat hidden by the one Thomas has fixed: Thomas has fixed
post-processing code after the stash has already been saved away. The
problem I'm referring to is a missing check for invalid paths before the
stash is saved away.
-Marc
