Re: Please default to 'commit -a' when no changes were added
- From
Michael Witten <mfwitten@gmail.com>
- Date
- Apr 23, 2010, 23:26 UTC
- Message-ID
- <k2tb4087cc51004231626jb9420742z33e8e95be608ac78@mail.gmail.com>
- In-Reply-To
- <4BD21CAB.8060903@gmx.de>
On Fri, Apr 23, 2010 at 17:18, Matthias Andree <matthias.andree@gmx.de> wrote:
Show 16 quoted lines
> Am 23.04.2010 21:34, schrieb Michael Witten: >> On Fri, Apr 23, 2010 at 13:59, Matthias Andree <matthias.andree@gmx.de> wrote: >>> I'd also concur that "default to commit -a" would be a most undesireable >> >> The proposal was not "default to commit -a" but rather "default to >> commit -a when the index has not been explicitly updated with >> something like git add". > > Which is the same: > > default (n) (5b) "a selection automatically used by a computer program > in the absence of a choice made by the user" (Merriam-Webster) > > No previous "git add" => default "git commit -a". Exactly what I don't > want. It makes the software appear at nondeterministic as you add to > the "if"s and "but"s, and it breaks established practice.
It wasn't at all clear that's what you meant.
> It is not desirable to break established workflows for the sake of > newcomers' convenience.
It's not entirely clear (to me) that Goswin's proposal really breaks established workflow.