On Thu, 30 Nov 2006 19:47:16 +0100, Jakub Narebski wrote: > while in git "git add" means "I want to add this file" (in the state > it is now) and not "I want the system to 'know' about this file". > And "commit" mean "Please commit the current 'known' state of all > files (or/and the current state of files I mention here on the > comand line)". Yes. There is a logical explanation for what git does, and it is self-consistent. It just means that the user is _forced_ to pass file state across the: "working tree" -> git boundary at two different times with two different commands for the very first commit the user makes. And the user _must_ understand that this is a two-step process, (even though, without the "typo" in my example above it would be natural to conclude the transition occurred only during "commit"). See? Git _is_ harder to learn, and a user really cannot learn it without being careful about the index right from the very beginning. -Carl
Attachment:
pgpgA5GFXGUI3.pgp
Description: PGP signature