From: Kevin Daudt <me@ikke.info>
To: Peter Urda <peter.urda@gmail.com>
Cc: git@vger.kernel.org
Subject: 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"
Date: Wed, 30 Nov 2016 22:11:00 +0100 [thread overview]
Message-ID: <20161130211100.GA18680@ikke.info> (raw)
In-Reply-To: <CAEnOLdvG=SoKFxeJ_pLmamGj_8osC+28TSg+pbFLLTr+ZLcpQA@mail.gmail.com>
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.
next prev parent reply other threads:[~2016-11-30 21:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 20:31 "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" Peter Urda
2016-11-30 21:11 ` Kevin Daudt [this message]
2016-11-30 22:04 ` Junio C Hamano
2016-11-30 22:40 ` Junio C Hamano
2016-12-06 18:04 ` Brandon Williams
2016-12-06 21:21 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161130211100.GA18680@ikke.info \
--to=me@ikke.info \
--cc=git@vger.kernel.org \
--cc=peter.urda@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.