From: Matthieu Moy Date: Wed, 02 Feb 2011 18:15:37 GMT Subject: Re: [1.8.0] git-stash invocation changes Message-ID: In-Reply-To: Shawn Pearce writes: > On Wed, Feb 2, 2011 at 09:23, Thomas Rast wrote: >> Proposal: >> >> 1. Change 'git stash ' to give a usage message >>   instead of using as the stash message. > > Oh please, yes, please do this. We should have done this long, long > ago. Its easy enough to train your fingers or fix your scripts to say > `git stash save list` rather than `git stash lsit` once stash errors > out and gives you a usage message once. Err, hasn't this been fixed long ago already? $ git stash not-a-stash-command Usage: git stash list [] or: git stash show [] or: git stash drop [-q|--quiet] [] or: git stash ( pop | apply ) [--index] [-q|--quiet] [] or: git stash branch [] or: git stash [save [--patch] [-k|--[no-]keep-index] [-q|--quiet] []] or: git stash clear $ git stash save --no-such-option error: unknown option for 'stash save': --no-such-option To provide a message, use git stash save -- '--no-such-option' Usage: [...] Only this could be seen as a problem: $ git stash save this-is-not-a-stash-name Saved working directory and index state On master: this-is-not-a-stash-name in particular, it is wrt: Thomas Rast writes: > 2. Change 'git stash -p ' to treat the as filename > arguments similar to add -p. Possibly add a -m option that lets > you specify a message anyway, if desired. I'm not a user of "stash with messages" myself, so I can't say how annoying the migration would be, but -m "message" sounds good to me. -- Matthieu Moy http://www-verimag.imag.fr/~moy/