Questions about transplant extension

[Neo Jia]

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?

Thanks,
Neo

On Wed, Mar 5, 2008 at 12:29 PM, Martin Geisler <mg at daimi.au.dk> wrote:
> "Neo Jia" <neojia at gmail.com> writes:
>
>  Hello,
>
>
>  > 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."
>
>  --
>  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
>  http://selenic.com/mailman/listinfo/mercurial
>
>



-- 
I would remember that if researchers were not ambitious
probably today we haven't the technology we are using!