Re: [PATCH 0/2] Making "git commit" to mean "git commit -a".

From: Junio C Hamano <junkio@cox.net>
Date: Nov 30, 2006, 01:22 UTC
Message-ID: <7vk61dn2yj.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <7vodqpn3t4.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano <junkio@cox.net> writes:

Show 7 quoted lines

> ...  Rather,
> "building your next commit incrementally in the index is the
> workflow git is designed to support, but you are not required to
> do that _incrementally_.  Until you encounter a complex
> situation such as resolving a large conflicting merge, doing
> that incrementally does not buy you anything as long as you work
> in a clean working tree.

Side note. I think the above "Until..." is an overstatement, and maybe the readers of the tutorial can be taught a lot earlier how the index can help them. Maybe the following sequence can be added to an early part of the tutorial sequence?

 $ edit hello.c
 $ make test
 $ git diff
 $ git update-index hello.c; # ok, that is good so far.
 $ edit hello.c; # hack more
 $ make test; # oops, does not work
 $ git diff; # ah, that overeager edit broken what was good
 $ git checkout hello.c; # get the last good one back