[issue1604] transplant --continue fails if commit message starts with #

Stefano Tortarolo mercurial-bugs at selenic.com
Thu Apr 9 05:12:45 CDT 2009


New submission from Stefano Tortarolo <stefano.tortarolo at gmail.com>:

Reported in ml by Derek Yang

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.

I'm adding djc and brendan (transplant's author) to nosy list.

----------
messages: 9041
nosy: astratto, brendan, djc, dyang
priority: bug
status: unread
title: transplant --continue fails if commit message starts with #
topic: transplant

____________________________________________________
Mercurial issue tracker <mercurial-bugs at selenic.com>
<http://www.selenic.com/mercurial/bts/issue1604>
____________________________________________________



More information about the Mercurial-devel mailing list