immutable commit messages, why?

[Dustin Sallings]

On Mar 19, 2008, at 11:33, Stuart McGraw wrote:

> Why are commit messages immutable?  They are (in theory) not really  
> part of the state of a set of files but rather meta-information  
> about that state, yes?
>
> This issue is preventing my adoption of a DVCS.  I have a CVS  
> repository in which a number of commit message are wrong,  
> misleading, vague, or otherwise sub-par.  I not infrequently need to  
> find previous work based on these messages.  As I find problems or  
> have time, I fix bad commit messages by editing the CVS repo files  
> in-place.  But once I import this repo into Mercurial (or any other  
> free DVCS AFAIK [1]) the commit messages will be set in stone for  
> all eternity, so I have put off making the jump.


	Your description also sounds like it applies to the code itself, or  
comments within the code, or the changeset author, or the date.

	It's all the same to me.

-- 
Dustin Sallings

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/mercurial/attachments/20080319/321395c1/attachment.htm