|
9 | 9 | --------
|
10 | 10 | [verse]
|
11 | 11 | 'git stash' list [<options>]
|
12 |
| -'git stash' (show | drop | pop ) [<stash>] |
13 |
| -'git stash' apply [--index] [<stash>] |
| 12 | +'git stash' ( show | drop ) [<stash>] |
| 13 | +'git stash' ( pop | apply ) [--index] [<stash>] |
14 | 14 | 'git stash' branch <branchname> [<stash>]
|
15 | 15 | 'git stash' [save [--keep-index] [<message>]]
|
16 | 16 | 'git stash' clear
|
@@ -86,16 +86,16 @@ Applying the state can fail with conflicts; in this case, it is not
|
86 | 86 | removed from the stash list. You need to resolve the conflicts by hand
|
87 | 87 | and call `git stash drop` manually afterwards.
|
88 | 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. |
94 |
| -+ |
95 | 89 | If the `--index` option is used, then tries to reinstate not only the working
|
96 | 90 | tree's changes, but also the index's ones. However, this can fail, when you
|
97 | 91 | have conflicts (which are stored in the index, where you therefore can no
|
98 | 92 | longer apply the changes as they were originally).
|
| 93 | ++ |
| 94 | +When no `<stash>` is given, `stash@\{0}` is assumed. |
| 95 | + |
| 96 | +apply [--index] [<stash>]:: |
| 97 | + |
| 98 | + Like `pop`, but do not remove the state from the stash list. |
99 | 99 |
|
100 | 100 | branch <branchname> [<stash>]::
|
101 | 101 |
|
|
0 commit comments