Questions about transplant extension
neojia at gmail.com
Thu Mar 6 13:34:59 CST 2008
On Thu, Mar 6, 2008 at 9:54 AM, Martin Geisler <mg at daimi.au.dk> wrote:
> "Neo Jia" <neojia at gmail.com> writes:
> >> > I am thinking if the transplant extension can keep record which
> >> > changeset has been transplanted. Also, it would be nice to have a
> >> > transplant "guard" to do this automatically.
> >> As far as I know, the transplant extension already does what you
> >> want. See the first section here:
> >> http://www.selenic.com/mercurial/wiki/index.cgi/TransplantExtension
> >> "It records the original changeset ID in the transplanted
> >> changeset, and avoids transplanting previously-transplanted
> >> patches."
> > But, if you clone that "transplanted" repository, you cannot continue
> > your later "transplant" in the new cloned repo, right?
> > So, is there anyway make the transplant distributed?
> I have actually not used transplant that much, I just read the manual
> and wiki... but why don't you try it our yourself on some local clones?
I have tried it on local clones but it cannot keep record of the
transplanted changeset in cloned repository.
> Martin Geisler
> VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
> SMPC (Secure Multi-Party Computation) to Python. See: http://viff.dk/.
> Mercurial mailing list
> Mercurial at selenic.com
I would remember that if researchers were not ambitious
probably today we haven't the technology we are using!
More information about the Mercurial