[Bug report] hg transplant --continue fails if check-in message starts with "#"

[Derek Yang]

Hi,

We run into this issue today.  If manual merge is required during
transplant, and if the check-in message of the changeset being transplanted
starts with a "#" (e.g. #1234 - blahblahblah), then transplant --continue
will fail with the following message:

abort: transplant log file is corrupt

It seems that "#" is considered to be a metadata keyword by transplant.

Our work-around is to manually hack the .hg/transplant/journal file to add
some words in front of "#" so the check-in message metadata is correctly
recognized by hg.

This happens on both hg v1.1.2 and v1.2.1.

Please let me know if you need any information.

Thanks,

Derek Yang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/mercurial/attachments/20090409/256abfa2/attachment.htm