Amending a changeset

[Christian Boos]

Ok, it seems I misunderstood your original purpose, you don't want to 
only redo the latest changeset (a la git commit --amend), but rework any 
group of related changesets.

Leslie P. Polzer wrote:
> ...
>> 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?
>   

With patch queues - see the hg book 
(http://hgbook.red-bean.com/hgbookch12.html), the EditingHistory page 
that Paul already mentioned earlier in this thread and maybe you should 
go through the following discussion in the Mercurial ML archive: 
http://selenic.com/pipermail/mercurial/2008-April/018447.html

-- Christian