From: Jacob Helwig <jacob.helwig@gmail.com>
Date: Sat, 24 Apr 2010 19:35:38 GMT
Subject: Re: 'commit -a' safety (was: Re: Please default to 'commit -a' when no changes were added)
Message-ID: <r2y8c9a061004241235n77ca3925q8fde8fc3b01e4e80@mail.gmail.com>
In-Reply-To: <20100424185433.GN3563@machine.or.cz>

On Sat, Apr 24, 2010 at 11:54, Petr Baudis <pasky@suse.cz> wrote:
> Are there valid user scenarios where you customize your index, then want
> to override that using -a without thinking twice?
>

Depends on what you consider "customizing your index".  I add files to
the index all the time as I'm working on things, then commit -a at the
end "without thinking twice".

For example:
1) Hack on something.
2) git add $thing
3) Run full test-suite.
4) Fix a failing module.
5) git add $fixed-module-and-tests
6) Repeat 3-5 until there's only one module failing.
7) Fix last failing module.
8) git commit -a

I doubt I'm the only one that stages things as a way of marking them
as "done", and using git commit -a to "check-off" the last "todo"
item.