From: Daniel Lublin <daniel@lublin.se>
To: git@vger.kernel.org
Subject: git stash push --patch offers skip-worktree hunks
Date: Wed, 27 Jan 2021 08:15:19 -0000 (UTC) [thread overview]
Message-ID: <rur7en$16bk$1@ciao.gmane.io> (raw)
Hi,
I'm using this to hide some locally modified files from accidental commit:
git update-index --skip-worktree ...
Doing `git stash push` does not result in the above modifications being
stashed. But, doing `git stash push --patch` asks me about hunks in the
files which were flagged to skip-worktree. Instinctively, this feels wrong.
The docs also say:
Interactively select hunks from the diff between HEAD and the working tree
to be stashed.
What do you think?
regards,
--
Daniel
lublin.se
next reply other threads:[~2021-01-27 8:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 8:15 Daniel Lublin [this message]
2021-01-27 13:21 ` git stash push --patch offers skip-worktree hunks brian m. carlson
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='rur7en$16bk$1@ciao.gmane.io' \
--to=daniel@lublin.se \
--cc=git@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox