Amending a changeset

[Leslie P. Polzer]

> At a fundamental level, no, as in Mercurial, history is immutable. If
> your changeset has been distributed to other repositories, you can't
> get it back.

Fortunately (or not, from a social POV) I'm working alone and have
control over all instances of the repository.


> On a practical level, there are ways of doing this if you understand
> that you are *not* amending the existing changeset, but are rather
> replacing it with an altered changeset (with all the implications that
> has).

That's not really a problem. In this particular case it doesn't even
have to stay at the same position in the commit tree.


> You should also make sure you understand your motivations in wanting
> to edit this changeset. What does that give you that simply committing
> a new changeset which fixes the problem doesn't?

I like having my changes semantically grouped so I can label them like
“with this check-in I modified FOO to act like BAR instead of ZOO”
and easily go back to the previous chunk.


> In Mercurial, while
> individual changesets are important, they aren't quite the complete,
> self-contained entities that they seem to be in darcs. Maybe you don't
> need to do this at all, and it's just a hold-over from your ways of
> working in darcs?

Well -- how *would* I get the semantically closed groups in Mercurial
instead if not with changesets?

  Thanks a lot,

    Leslie