From: Junio C Hamano <gitster@pobox.com>
To: Yuri <yuri@tsoft.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: 'git stash push -- {dir}' puts files in stash that are outside of {dir}
Date: Wed, 26 Jul 2023 10:29:09 -0700 [thread overview]
Message-ID: <xmqqsf9ad1ju.fsf@gitster.g> (raw)
In-Reply-To: <5fce9c4f-0ea7-9393-4a30-ddd66946661d@tsoft.com> (yuri@tsoft.com's message of "Wed, 26 Jul 2023 10:05:04 -0700")
Yuri <yuri@tsoft.com> writes:
> I am in the FreeBSD ports repository.
>
> I run this command:
>
> $ git stash push -m "gh-print-tuple" -- Mk
>
> But then 'git show' shows that the top stash entry also has other files:
>
> $ git stash show -p stash@{0} | grep diff
Not offering a solution, as a quick test or two in my environment do
not reproduce this problem [*]. But instead of the above command,
which will show matches on any line that has "diff" in the "-p"
output, perhaps
$ git stash show --stat
is easier to see?
Are there configuration variables set to affect the behaviour of the
"git stash" command in your environment that I do not have (I have
nothing in "git config -l | grep stash" output), which may be
affecting why it does not reproduce for me?
> Why do files that are not under Mk get into stash?
[Footnote]
* Admittedly I didn't recall we had pathspec support to "git stash
push" so consider me no longer an expert in this area ;-).
next prev parent reply other threads:[~2023-07-26 17:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 17:05 'git stash push -- {dir}' puts files in stash that are outside of {dir} Yuri
2023-07-26 17:29 ` Junio C Hamano [this message]
2023-07-26 17:36 ` Yuri
2023-07-26 18:14 ` 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=xmqqsf9ad1ju.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=yuri@tsoft.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.