summaryrefslogtreecommitdiff
path: root/git-stash.sh
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2008-01-05 09:35:54 (GMT)
committerJunio C Hamano <gitster@pobox.com>2008-01-07 02:41:36 (GMT)
commit3023dc690f98f83b64cc6f2a9cc015bf2b01964a (patch)
tree9f56b0da7a3c138bb00036a63d53ba281f3d9ed6 /git-stash.sh
parent7c390d90e8b6322948f45cecc658d62813c0d5ae (diff)
downloadgit-3023dc690f98f83b64cc6f2a9cc015bf2b01964a.zip
git-3023dc690f98f83b64cc6f2a9cc015bf2b01964a.tar.gz
git-3023dc690f98f83b64cc6f2a9cc015bf2b01964a.tar.bz2
git-stash clear: refuse to work with extra parameter for now
Because it is so tempting to expect "git stash clear stash@{4}" to remove the fourth element in the stash while leaving other elements intact, we should not blindly throw away everything upon seeing such a command. This may change when we start using "git reflog delete" to selectively nuke a single (or multiple, for that matter) stash entries with such a command line. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'git-stash.sh')
-rwxr-xr-xgit-stash.sh7
1 files changed, 6 insertions, 1 deletions
diff --git a/git-stash.sh b/git-stash.sh
index 4d5e5c0..b00f888 100755
--- a/git-stash.sh
+++ b/git-stash.sh
@@ -20,6 +20,10 @@ no_changes () {
}
clear_stash () {
+ if test $# != 0
+ then
+ die "git stash clear with parameters is unimplemented"
+ fi
if current=$(git rev-parse --verify $ref_stash 2>/dev/null)
then
git update-ref -d $ref_stash $current
@@ -216,7 +220,8 @@ apply)
apply_stash "$@"
;;
clear)
- clear_stash
+ shift
+ clear_stash "$@"
;;
create)
if test $# -gt 0 && test "$1" = create