If you are talking about "git commit file1 file2" ignoring the current
index, and building a new index just updating file1 and file2 from the
working directory, I disagree that it was a big mistake.
Actually, I was very happy to get that change (IIRC it was me requesting
it, so blame me), because I now can say: just specify exactly what you
want to commit *1*.
If you want to commit just file2 (even if you added file1, but did not
commit it yet) do "git commit file2". If you want to commit all changes,
either pass the names of all modified files, or "-a". IMHO this satisfies
the principle of least surprise.
Ciao,
Dscho
Footnote 1: Of course, you can use commit in more ways. But this is
sufficient to get people started.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html