Re: "git add -p ." raises an unexpected "warning: empty strings as pathspecs will be made invalid in upcoming releases. please use . instead if you meant to match all paths"

From: Junio C Hamano <gitster@pobox.com>
Date: Dec 6, 2016, 21:21 UTC
Message-ID: <xmqqlgvszrco.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <20161206180400.GA103573@google.com>

Brandon Williams <bmwill@google.com> writes:

Show 12 quoted lines

> On 11/30, Junio C Hamano wrote:
>> Junio C Hamano <gitster@pobox.com> forgot to Cc: the author of the
>> most relevant change to the issue, d426430e6e ("pathspec: warn on
>> empty strings as pathspec", 2016-06-22).
>> ...
>
> I've been doing a bit of work trying to clean up the pathspec
> initialization code and I believe this can be fixed without
> having to add in this work around.  The code which does the munging is
> always trying to prefix the pathspec regardless if there is a prefix or
> not.  If instead its changed to only try and prefix the original if
> there is indeed a prefix, then it should fix the munging.

Thanks; sounds like a plan.