[PATCH v2 0/3] Re: [BUG] "git stash -- path" reports wrong unstaged changes
- From
Thomas Gummerer <t.gummerer@gmail.com>
- Date
- Mar 21, 2017, 22:12 UTC
- Message-ID
- <20170321221219.28041-1-t.gummerer@gmail.com>
- In-Reply-To
- <20170319202351.8825-1-t.gummerer@gmail.com>
Thanks Junio and Peff for comments and suggestions on the previous round.
Changes since v1: - 1/3 now contains the changes that were previously split up into 1/3 and 2/3, and also makes git reset --hard in the simple 'git stash' case quiet unconditionally. - 2/3 is what was 3/3 in the previous round, and now includes a test for the expected behaviour. - 3/3 is the fix for the bug Peff noticed for git stash -k with changes that are not yet in the index.
Thomas Gummerer (3): stash: don't show internal implementation details stash: pass the pathspec argument to git reset stash: keep untracked files intact in stash -k
git-stash.sh | 12 +++++++----- t/t3903-stash.sh | 16 +++++++++++++++- t/t3904-stash-patch.sh | 8 ++++++++ 3 files changed, 30 insertions(+), 6 deletions(-)
-- 2.12.0.401.g98d3b1bb99.dirty