From: Phil Hord Date: Tue, 21 Nov 2017 23:05:23 +0000 (-0800) Subject: doc: prefer 'stash push' over 'stash save' X-Git-Tag: v2.16.0-rc0~73^2 X-Git-Url: https://git.lorimer.id.au/gitweb.git/diff_plain/0d5f844f0a6c73df21d5ce940082a1a034703a6e?ds=inline;hp=--cc 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 Reviewed-by: Jonathan Nieder Signed-off-by: Junio C Hamano --- 0d5f844f0a6c73df21d5ce940082a1a034703a6e diff --git a/Documentation/git-stash.txt b/Documentation/git-stash.txt index 8be661007d..056dfb8661 100644 --- a/Documentation/git-stash.txt +++ b/Documentation/git-stash.txt @@ -175,14 +175,14 @@ create:: return its object name, without storing it anywhere in the ref namespace. This is intended to be useful for scripts. It is probably not - the command you want to use; see "save" above. + the command you want to use; see "push" above. store:: Store a given stash created via 'git stash create' (which is a dangling merge commit) in the stash ref, updating the stash reflog. This is intended to be useful for scripts. It is - probably not the command you want to use; see "save" above. + probably not the command you want to use; see "push" above. DISCUSSION ----------