On Wed, Nov 30, 2016 at 12:31:49PM -0800, Peter Urda wrote: > After upgrading to version 2.11.0 I am getting a warning about empty > strings as pathspecs while using 'patch' > > - Ran 'git add -p .' from the root of my git repository. > > - I was able to normally stage my changes, but was presented with a > "warning: empty strings as pathspecs will be made invalid in upcoming > releases. please use . instead if you meant to match all paths" > message. > > - I expected no warning message since I included a "." with my original > command. > > I believe that I should not be seeing this warning message as I > included the requested "." pathspec. > > ~ Peter Urda > > http://urda.cc
I can reproduce this. Note that it only happens when you specify '-p'. Without the --patch option, the warning does not appear.
