Re: git-stash: RFC: Adopt the default behavior to other commands
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Dec 18, 2007, 18:03 UTC
- Message-ID
- <Pine.LNX.4.64.0712181803070.23902@racer.site>
- In-Reply-To
- <871w9jrjdm.fsf@osv.gnss.ru>
Hi,
On Tue, 18 Dec 2007, Sergei Organov wrote:
Show 24 quoted lines
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes: > > > 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. > > ... allowing you to abort the operation by means of providing empty > commit message. On the other hand, "git stash" has immediate effect, so > it's somewhat more dangerous. Just to be picky, anyway.
Sorry, I have no time for this kind of discussions.
Ciao, Dscho