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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Tue, 18 Dec 2007, Sergei Organov wrote:

> Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes:
>
> > On Tue, 18 Dec 2007, Andreas Ericsson wrote:
> >
> >> Jakub Narebski wrote:
> >>
> >> > Andreas Ericsson <ae@xxxxxx> 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

-
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

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux