From: Brian Downing Date: Wed, 07 Nov 2007 00:26:45 GMT Subject: [PATCH] Disable implicit 'save' argument for 'git stash' Message-ID: <1194395205-27905-2-git-send-email-bdowning@lavos.net> In-Reply-To: <1194395205-27905-1-git-send-email-bdowning@lavos.net> Having 'git stash random stuff' actually stash changes is poor user interface, due to the likelyhood of misspelling another legitimate argument. Require an explicit 'save' command instead. Signed-off-by: Brian Downing --- This commit can be applied on top of the previous whenever it is decided "enough time" has passed for the hard behavior change of "git stash" to take place. git-stash.sh | 16 +++++----------- t/t3903-stash.sh | 4 ++-- 2 files changed, 7 insertions(+), 13 deletions(-) diff --git a/git-stash.sh b/git-stash.sh index a8b854a..e900d40 100755 --- a/git-stash.sh +++ b/git-stash.sh @@ -219,17 +219,11 @@ create) help | usage) usage ;; -*) - if test $# -gt 0 && test "$1" = save - then - shift - else - cat >&2 < file && test_tick && git stash ' -test_expect_success 'stash with bare message' ' +test_expect_failure 'stash with bare message' ' echo 8 > file && test_tick && git stash "a message" -- 1.5.3.5.1547.gf6d81-dirty