[Python-Dev] Mercurial migration readiness

[Éric Araujo]

[Martin Geisler]
> You basically need to replay the changes -- the transplant extension can
> do this for you. This is more or less a wrapper around 'hg export'
> (gives you a diff) and 'hg import' (applies the diff).

Core developers seem to be okay with svnmerge, so perhaps a
familiar-looking command like transplant (with “merges” that are
actually replays, and explicit blocking for bookkeeping) will feel right
to them.

> It sounds like you are describing how Mercurial itself was developed
> before we began using named branches.

Spot on, sir!

> [snip] You'll notice the small labels saying 'stable' on the changesets
> from that branch -- that is the whole difference.

Thanks for the explanation. The new workflow seems quite good.

Regards