A stash may store not only working tree changes, but also
changes to the index. However, "git stash show" will only
ever show the working tree changes. We can instead show both
as a combined diff, but use "--simplify-combined-diff" so
that we show a normal pairwise diff in the common case that
there were no index changes.
Signed-off-by: Jeff King <peff@xxxxxxxx>
---
I'm still a little iffy on this one in case somebody really doesn't want
to see the saved index state. But with the earlier cleanups, you can at
least see that it doesn't even impact any existing tests.
git-stash.sh | 3 ++-
t/t3903-stash.sh | 22 ++++++++++++++++++++++
2 files changed, 24 insertions(+), 1 deletion(-)
diff --git a/git-stash.sh b/git-stash.sh
index a0246d5..ae73ba4 100755
--- a/git-stash.sh
+++ b/git-stash.sh
@@ -304,7 +304,8 @@ list_stash () {
show_stash () {
assert_stash_like "$@"
- git diff ${FLAGS:---stat} $b_commit $w_commit
+ git show --format= --simplify-combined-diff \
+ ${FLAGS:---stat} $w_commit
}
#
diff --git a/t/t3903-stash.sh b/t/t3903-stash.sh
index 465f824..36b97a4 100755
--- a/t/t3903-stash.sh
+++ b/t/t3903-stash.sh
@@ -537,6 +537,28 @@ test_expect_success 'stash show -p - no stashes on stack, stash-like argument' '
test_cmp expected actual
'
+test_expect_success 'stash show -p will show modified index' '
+ git stash clear &&
+ test_when_finished "git reset --hard HEAD" &&
+ git reset --hard &&
+ echo index >file &&
+ git add file &&
+ echo working >file &&
+ git stash &&
+ cat >expect <<-\EOF &&
+ diff --cc file
+ index 7601807,9015a7a..d26b33d
+ --- a/file
+ +++ b/file
+ @@@ -1,1 -1,1 +1,1 @@@
+ - baz
+ -index
+ ++working
+ EOF
+ git stash show -p >actual &&
+ test_cmp expect actual
+'
+
test_expect_success 'stash drop - fail early if specified stash is not a stash reference' '
git stash clear &&
test_when_finished "git reset --hard HEAD && git stash clear" &&
--
2.1.0.rc0.286.g5c67d74
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html