From: Marc Strapetz <marc.strapetz@syntevo.com>
To: Thomas Gummerer <t.gummerer@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git stash push -u always warns "pathspec '...' did not match any files"
Date: Sun, 4 Mar 2018 11:44:30 +0100 [thread overview]
Message-ID: <08d765ec-b2d7-7087-fca5-2eecefcef9cf@syntevo.com> (raw)
In-Reply-To: <20180303154654.GH2130@hank>
On 03.03.2018 16:46, Thomas Gummerer wrote:
> On 03/03, Marc Strapetz wrote:
>> Reproducible in a test repository with following steps:
>>
>> $ touch untracked
>> $ git stash push -u -- untracked
>> Saved working directory and index state WIP on master: 0096475 init
>> fatal: pathspec 'untracked' did not match any files
>> error: unrecognized input
>>
>> The file is stashed correctly, though.
>>
>> Tested with Git 2.16.2 on Linux and Windows.
>
> Thanks for the bug report and the reproduction recipe. The following
> patch should fix it:
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. For example:
$ git stash push -u -- nonexisting
Saved working directory and index state WIP on master: 171081d initial
import
I would probably expect to see an error message as for:
$ git stash push -- nonexisting
error: pathspec 'nonexisting' did not match any file(s) known to git.
Did you forget to 'git add'?
That said, this is no problem for us, because I know that the paths I'm
providing to "git stash push" do exist. I just wanted to point out.
-Marc
next prev parent reply other threads:[~2018-03-04 10:44 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-03 9:44 git stash push -u always warns "pathspec '...' did not match any files" Marc Strapetz
2018-03-03 15:46 ` Thomas Gummerer
2018-03-04 10:44 ` Marc Strapetz [this message]
2018-03-09 22:18 ` Junio C Hamano
2018-03-10 9:18 ` Marc Strapetz
2018-03-10 11:12 ` Thomas Gummerer
2018-03-14 21:46 ` [PATCH v2 1/2] stash push: avoid printing errors Thomas Gummerer
2018-03-14 21:46 ` [PATCH v2 2/2] stash push -u: don't create empty stash Thomas Gummerer
2018-03-15 20:09 ` Junio C Hamano
2018-03-16 20:10 ` Thomas Gummerer
2018-03-15 8:51 ` [PATCH v2 1/2] stash push: avoid printing errors Marc Strapetz
2018-03-16 20:12 ` Thomas Gummerer
2018-03-16 20:43 ` [PATCH v3 0/2] stash push -u -- <pathspec> fixes Thomas Gummerer
2018-03-16 20:43 ` [PATCH v3 1/2] stash push: avoid printing errors Thomas Gummerer
2018-03-16 21:31 ` Junio C Hamano
2018-03-16 20:43 ` [PATCH v3 2/2] stash push -u: don't create empty stash Thomas Gummerer
2018-03-16 22:37 ` [PATCH v4 0/3] stash push -u -- <pathspec> fixes Junio C Hamano
2018-03-16 22:37 ` [PATCH v4 1/3] stash: fix nonsense pipeline Junio C Hamano
2018-03-16 22:37 ` [PATCH v4 2/3] stash push: avoid printing errors Junio C Hamano
2018-03-16 22:37 ` [PATCH v4 3/3] stash push -u: don't create empty stash Junio C Hamano
2018-03-17 11:36 ` [PATCH v4 0/3] stash push -u -- <pathspec> fixes Thomas Gummerer
2018-03-19 23:21 ` [PATCH v5 " Thomas Gummerer
2018-03-19 23:21 ` [PATCH v5 1/3] stash: fix nonsense pipeline Thomas Gummerer
2018-03-19 23:21 ` [PATCH v5 2/3] stash push: avoid printing errors Thomas Gummerer
2018-03-20 16:54 ` Junio C Hamano
2018-03-21 21:36 ` Thomas Gummerer
2018-03-21 21:53 ` [PATCH] stash: drop superfluos pathspec parameter (was: Re: [PATCH v5 2/3] stash push: avoid printing errors) Thomas Gummerer
2018-03-21 22:07 ` [PATCH] stash: drop superfluos pathspec parameter Junio C Hamano
2018-03-21 21:56 ` [PATCH v5 2/3] stash push: avoid printing errors Junio C Hamano
2018-03-19 23:21 ` [PATCH v5 3/3] stash push -u: don't create empty stash Thomas Gummerer
2018-03-20 10:06 ` [PATCH v5 0/3] stash push -u -- <pathspec> fixes Marc Strapetz
2018-03-19 15:44 ` [PATCH v3 0/2] " Marc Strapetz
2018-03-19 21:51 ` Thomas Gummerer
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=08d765ec-b2d7-7087-fca5-2eecefcef9cf@syntevo.com \
--to=marc.strapetz@syntevo.com \
--cc=git@vger.kernel.org \
--cc=t.gummerer@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).