The command requires an explicit "save" subcommand, but the usage string does not talk about it.
This matches the usage string with the SYNOPSIS string in the documentation.
Signed-off-by: Nanako Shiraishi <nanako3@bluebottle.com> ---
I do not know if my opinion matters much but I think it is nicer to save a new stash without a subcommand than to list existing stash data.
git-stash.sh | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)
Show changes to git-stash.sh +1 −1
diff --git a/git-stash.sh b/git-stash.sh index 18d3322..62f9f7a 100755 --- a/git-stash.sh +++ b/git-stash.sh @@ -1,7 +1,7 @@ #!/bin/sh # Copyright (c) 2007, Nanako Shiraishi -USAGE='[ | list | show | apply | clear]' +USAGE='(save | list | show [<stash>] | apply [<stash>] | clear)' . git-sh-setup require_work_tree
-- 1.5.2 -- Nanako Shiraishi http://ivory.ap.teacup.com/nanako3/ ---------------------------------------------------------------------- Find out how you can get spam free email. http://www.bluebottle.com