Skip to content

Commit db8af4b

Browse files
committed
Merge branch 'tr/maint-doc-stash-pop' into maint
* tr/maint-doc-stash-pop: Documentation: teach stash/pop workflow instead of stash/apply
2 parents 6a01554 + 7b8988e commit db8af4b

File tree

2 files changed

+18
-16
lines changed

2 files changed

+18
-16
lines changed

Documentation/git-stash.txt

Lines changed: 16 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -75,14 +75,22 @@ show [<stash>]::
7575
it will accept any format known to 'git-diff' (e.g., `git stash show
7676
-p stash@\{1}` to view the second most recent stash in patch form).
7777

78-
apply [--index] [<stash>]::
78+
pop [<stash>]::
7979

80-
Restore the changes recorded in the stash on top of the current
81-
working tree state. When no `<stash>` is given, applies the latest
82-
one. The working directory must match the index.
80+
Remove a single stashed state from the stash list and apply it
81+
on top of the current working tree state, i.e., do the inverse
82+
operation of `git stash save`. The working directory must
83+
match the index.
8384
+
84-
This operation can fail with conflicts; you need to resolve them
85-
by hand in the working tree.
85+
Applying the state can fail with conflicts; in this case, it is not
86+
removed from the stash list. You need to resolve the conflicts by hand
87+
and call `git stash drop` manually afterwards.
88+
+
89+
When no `<stash>` is given, `stash@\{0}` is assumed. See also `apply`.
90+
91+
apply [--index] [<stash>]::
92+
93+
Like `pop`, but do not remove the state from the stash list.
8694
+
8795
If the `--index` option is used, then tries to reinstate not only the working
8896
tree's changes, but also the index's ones. However, this can fail, when you
@@ -112,12 +120,6 @@ drop [<stash>]::
112120
Remove a single stashed state from the stash list. When no `<stash>`
113121
is given, it removes the latest one. i.e. `stash@\{0}`
114122

115-
pop [<stash>]::
116-
117-
Remove a single stashed state from the stash list and apply on top
118-
of the current working tree state. When no `<stash>` is given,
119-
`stash@\{0}` is assumed. See also `apply`.
120-
121123
create::
122124

123125
Create a stash (which is a regular commit object) and return its
@@ -163,7 +165,7 @@ $ git pull
163165
file foobar not up to date, cannot merge.
164166
$ git stash
165167
$ git pull
166-
$ git stash apply
168+
$ git stash pop
167169
----------------------------------------------------------------
168170

169171
Interrupted workflow::
@@ -192,7 +194,7 @@ You can use 'git-stash' to simplify the above, like this:
192194
$ git stash
193195
$ edit emergency fix
194196
$ git commit -a -m "Fix in a hurry"
195-
$ git stash apply
197+
$ git stash pop
196198
# ... continue hacking ...
197199
----------------------------------------------------------------
198200

Documentation/user-manual.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1520,10 +1520,10 @@ $ git commit -a -m "blorpl: typofix"
15201520
------------------------------------------------
15211521

15221522
After that, you can go back to what you were working on with
1523-
`git stash apply`:
1523+
`git stash pop`:
15241524

15251525
------------------------------------------------
1526-
$ git stash apply
1526+
$ git stash pop
15271527
------------------------------------------------
15281528

15291529

0 commit comments

Comments
 (0)