Validating commit message in central repository

[Haszlakiewicz, Eric]

>-----Original Message-----
>From: Matt Mackall [mailto:mpm at selenic.com]
>> Mercurial makes it very hard to change anything about a changeset
after
>> it's been committed.  To actually adjust the message you're best bet
is
>> probably to use "hg transplant" with the --filter option, and write a
>> script that sets the message you want.  Then strip the offending
>> changeset(s).
>
>Please recommend pull -r rather than strip on this list. Pull is
>built-in non-destructive functionality, strip is in an extension and is
>a good way for new users to lose data.

Ok, but it doesn't seem to work for me.  I tried using pull -r, but it
still ends up "requesting all changes".  I guess I'll need to play
around with it a bit to figure out what I'm doing wrong.

I find strip to be much easier to think about when removing things than
having to invert my logic, plus it's much faster than making yet another
clone.  You can always re-add the backup bundle that strip creates, so
unless you specify --nobackup you aren't actually losing data.

hmm... it occurs to me that an interactive mode for strip might go a
long way towards making it less error prone.  (not that I have time to
try to implement something like that)

eric