Re: git-stash: RFC: Adopt the default behavior to other commands

[Johannes Schindelin <Johannes.Schindelin@gmx.de>]

Hi,

On Tue, 18 Dec 2007, Andreas Ericsson wrote:

> Jakub Narebski wrote:
>
> > Andreas Ericsson <ae@op5.se> writes:
> >
> > > My point is that it would be nice if all git commands that actually 
> > > manipulate objects (create/delete/modify) had a safe default, and 
> > > that experienced users such as yourself could endure the 
> > > insufferable agony of retraining your fingers to type five more 
> > > chars so that people won't have to get bitten by surprises.
> > 
> > Also for "git commit"?
> 
> git commit has a very safe default; It runs "git status" and exits.

Not in my universe.  It starts an editor, and then commits what I staged.

> > In my opinion _basic_ usage of git-stash is simply using it with one 
> > stash only: "git stash" / "git unstash" (i.e. "git stash apply"; by 
> > the way this is one (beside "git view") use case for builtin 
> > predefined aliases).  Using it with multiple stashes (only then "git 
> > stash list" is needed) is advanced usage; and for advanced usage 
> > longer form is preferred, I think.
> > 
> 
> Perhaps. I'll stop quibbling about it. I don't care very deeply about it 
> anyway.

Ah.  That explains why you made a case against the default operation ;-)

Ciao,
Dscho