immutable commit messages, why?

Andreas Axelsson andreas.axelsson at gmail.com
Thu Mar 20 06:07:09 CDT 2008


IMO if there was a way to modify commit messages I think it should be
append-only. I've sometimes wished for a way to change commit messages in
Perforce, which I use at work, but I'd rather not have people remove
information once it's there.

/axl

-----Original Message-----
From: mercurial-bounces at selenic.com [mailto:mercurial-bounces at selenic.com]
On Behalf Of Jens.Wulf at sew-eurodrive.de
Sent: den 20 mars 2008 07:29
To: smcg4191 at frii.com; mercurial at selenic.com
Subject: Re: immutable commit messages, why?

Maybe it is possible to write an extension which lets you save edited commit
messages to a versioned file (only containing pairs of changeset hash and
new commit messages, similar to .tags) and -- if enabled -- replace original
commit messages with those from the file (if they are overwritten there).
You have original commit messages that way, but also polished ones including
their history.

Best regards,
Jens


SEW-EURODRIVE GmbH & Co KG
Kommanditgesellschaft, Sitz: Bruchsal, RG Mannheim HRA 230970
Komplementärin: SEW-EURODRIVE Verwaltungs-GmbH, Sitz: Bruchsal, RG Mannheim
HRB 230207

Gesellschafter und Geschäftsführer: Rainer Blickle, Jürgen Blickle
Geschäftsführer: Johann Soder, Hans Sondermann, Bernd P. Uckrow




_______________________________________________
Mercurial mailing list
Mercurial at selenic.com
http://selenic.com/mailman/listinfo/mercurial




More information about the Mercurial mailing list