Re: Question about "git commit -a"

From: Matthieu Moy <matthieu.moy@imag.fr>
Date: Oct 5, 2007, 10:11 UTC
Message-ID: <vpqy7ehj2g8.fsf@bauges.imag.fr>
In-Reply-To: <47060BB3.3030208@op5.se>

Andreas Ericsson <ae@op5.se> writes:

> Yes, but it's so enormously powerful once you get a grip on it that I can't
> for the life of me imagine an scm system without it. You just can't do
> "scm commit --interactive" without it in a sane way,

darcs|hg record do a very similar job. The real difference between darcs and others here is not "scm commit --interactive", but the fact that you can split the work among multiple commands, the index maintains a persistant state.

> or check which merge- conflicts you've already resolved,

At least bzr and baz have this kind of conflict management. It's just a separate file, containing the list of unresolved conflicts.

> or compare working tree with what the next commit *will* look like,

To me, *that* is the point.

-- 
Matthieu