immutable commit messages, why?

Martin Geisler mg at daimi.au.dk
Thu Mar 20 12:45:37 CDT 2008


Will Maier <willmaier at ml1.net> writes:

> On Thu, Mar 20, 2008 at 11:30:27AM +0100, Martin Geisler wrote:
>> Put that way, then I agree with you. Currently you cannot do a commit if
>> nothing has changed, but if that was allowed, then I could imagine that
>> empty commits would be a way to amend the commit messages:
>> 
>>   hg status
>>   M foo.c
>>   hg commit -m 'Fixed bug.'          # Bad commit message.
>>   hg commit -f -m 'Fixed bug 123.'   # Better message.
>
> Is there some reason rollback or mq aren't applicable here?

In that example no, but I was thinking of adding the better log message
much later, after other people had committed things on top of the bad
commit.

But if you commit a changed commit message for an old changeset, then
you will end up with two heads which you'll have to merge. That will
probably look weird in 'hg view' :-(

-- 
Martin Geisler

VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multi-Party Computation) to Python. See: http://viff.dk/.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
Url : http://selenic.com/pipermail/mercurial/attachments/20080320/7a990348/attachment.pgp 


More information about the Mercurial mailing list