On Wed, Feb 2, 2011 at 11:51 AM, Thomas Rast <trast@xxxxxxxxxxxxxxx> wrote:
> Matthieu Moy wrote:
>> Shawn Pearce <spearce@xxxxxxxxxxx> writes:
>>
>> > On Wed, Feb 2, 2011 at 09:23, Thomas Rast <trast@xxxxxxxxxxxxxxx> wrote:
>> >> Proposal:
>> >>
>> >> 1. Change 'git stash <not-a-stash-command>' to give a usage message
>> >> instead of using <not-a-stash-command> 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?
>
> Oh, you're actually right. I have totally missed this, and should
> obviously have tested first.
>
> Still, I think the change to 'git stash -p' is also worthwhile.
>
There's still something annoyingly different about git-stash. Most git
commands that take sub-commands simply list useful information when
you don't provide a sub-command:
git branch --> lists local branches
git tag --> lists tags
git remote --> lists remotes
git stash --> creates a new stash
It would be much more predictable if git-stash without a sub-command
just listed the current stashes. But, at this point it's probably too
late to change that behavior.
> --
> Thomas Rast
> trast@{inf,student}.ethz.ch
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html