[issue1210] Problems when continuing 'transplant' in a cloned repository with transplants
Matti Hämäläinen
mercurial-bugs at selenic.com
Tue Jul 1 22:09:01 CDT 2008
New submission from Matti Hämäläinen <ccr at tnsp.org>:
The information in .hg/transplant/* (despite apparently somewhat redundant,
since the same information is also stored in the transplanted changesets) seems
to be used by transplant extension to determine which changesets have already
been transplated.
This results in awkwardness, if a repository with transplants (let's call it
repository "A") is cloned (into "B") and user tries to transplant more
changesets into "B" from the source repository - the extension does not know
that some of the changesets are already in "B", and begins the questionnaire
from scratch.
One way to resolve this would probably be to regenerate the files in
.hg/transplant , or clone them.
----------
messages: 6462
nosy: ccr
priority: wish
status: unread
title: Problems when continuing 'transplant' in a cloned repository with transplants
____________________________________________________
Mercurial issue tracker <mercurial-bugs at selenic.com>
<http://www.selenic.com/mercurial/bts/issue1210>
____________________________________________________
More information about the Mercurial-devel
mailing list