Hi,
On Mon, 2 Jul 2007, Jeff King wrote:
On Sun, Jul 01, 2007 at 02:54:00PM -0700, Junio C Hamano wrote:
quoted
I would further suggest that we _require_ 'git stash save' to create a
new one and perhaps make the non-subcommand case run 'git stash list'.
While I was trying the code out I accidentally created a new stash
when I did not mean to, which pushed the stash I wanted to apply down
in the list every time I made such a mistake.
I think that makes sense...it's somehow cleaner to me if the
non-subcommand case doesn't make any changes (maybe just because I like
to explore commands by running them).
I disagree entirely.
The _only_ default subcommand for git-stash, which makes _any_ sense, is
"save". I have run my own version of it several times, and it _literally_
was in those circumstances "hack, hack, hack, aargh, stash that, I'll need
it later". "git cherry-pick stash" and "git reflog show stash" were needed
far less.
I am utterly uninterested in the stash list.
Ciao,
Dscho