doc: prefer 'stash push' over 'stash save'
Although `git stash save` was deprecated recently, some parts of the documentation still refer to it instead of `push`. Signed-off-by: Phil Hord <phil.hord@gmail.com> Reviewed-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Phil Hord committed
Nov 21, 2017 at 15:05 UTC
0d5f844f0a6c73df21d5ce940082a1a034703a6e
1 file changed
+2
-2
Documentation/git-stash.txt
+2
-2
@@ -175,14 +175,14 @@ create::
175
return its object name, without storing it anywhere in the ref
176
namespace.
177
This is intended to be useful for scripts. It is probably not
178
- the command you want to use; see "save" above.
178
+ the command you want to use; see "push" above.
179
180
store::
181
182
Store a given stash created via 'git stash create' (which is a
183
dangling merge commit) in the stash ref, updating the stash
184
reflog. This is intended to be useful for scripts. It is
185
- probably not the command you want to use; see "save" above.
185
+ probably not the command you want to use; see "push" above.
186
187
DISCUSSION
188
----------