Hi, On Wed, 29 Nov 2006, Junio C Hamano wrote: > Junio C Hamano <junkio@xxxxxxx> writes: > > > ... 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 I like it. Sort of a "temporary commit" to check against. 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