cournape at gmail.com
Sun Apr 5 11:14:37 CEST 2009
On Sun, Apr 5, 2009 at 6:06 PM, "Martin v. Löwis" <martin at v.loewis.de> wrote:
>> Off the top of my head, the following is needed for a successful migration:
>> - Verify that the repository at http://code.python.org/hg/ is
>> properly converted.
> I see that this has four branches. What about all the other branches?
> Will they be converted, or not? What about the stuff outside /python?
> In particular, the Stackless people have requested that they move along
> with what core Python does, so their code should also be converted.
I don't know the capabilities of hg w.r.t svn conversion, so this may
well be overkill, but git has a really good tool for svn conversion
(svn-all-fast-export, developed by KDE). You can handle almost any svn
organization (e.g. outside the usual trunk/tags/branches), and convert
email addresses of committers, split one big svn repo into
subprojects, etc... Then, the git repo could be converted to hg
relatively easily I believe.
More information about the Python-Dev