Re: Please default to 'commit -a' when no changes were added

From: Tor Arntsen <tor@spacetec.no>
Date: Apr 24, 2010, 13:26 UTC
Message-ID: <q2ld2d39d861004240626hf7cfb5a4p1b6d7a594ef3d0fb@mail.gmail.com>
In-Reply-To: <k2ub4087cc51004231234z29228ac8ia0f62a4e16cedae4@mail.gmail.com>

On Fri, Apr 23, 2010 at 21:34, Michael Witten <mfwitten@gmail.com> wrote:

> 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".

For what it's worth, from another relative newcomer: The above would actually cause trouble sometimes for me. Having learned to use git add+git commit, and working on several things at once:

edit file1 edit file2 edit file3 git add file3 git commit -m"fixed file3"

In the above sequence (relative newcomer, but not entirely) I occasionally forget to do the 'git add file3' part (I just mistakenly thought I did). The way it works now means nothing happens, which is good. The way I understand the proposal I would instead end up with a commit of all my changed files, which is exactly not what I want. I can't stop thinking that it should be easy for anyone who wants the proposed behaviour to make an alias, or certainly a wrapper. Problem solved, without changing the way it works now.

-Tor