Hi, add this to .hgrc (or mercurial.ini on windows): [extensions] hgext.convert=
$ hg init newrepo $ hg convert http://svn.python.org/projects/stackless newrepo (this may take a loooong time, and you probably need to map authors to hg as well) $ cd newrepo $ hg push https://where.is.new.repo That should do the trick ;) Regards, alex. On Wed, Sep 7, 2011 at 11:40 PM, Richard Tew <[email protected]> wrote: > On Wed, Sep 7, 2011 at 9:20 PM, Herr Willert <[email protected]> wrote: >> are there any news about progress on migrating stackless to hg or on >> Stackless releases (especially 2.7.2 and 3.2.2)? >> >> The last info about these >> (http://www.stackless.com/pipermail/stackless/2011-June/005064.html) just >> says that you will move slowly. > > Beats me. The hg migration needs to be done before I can do any more > merges and releases. And as far as I know that's waiting on some > other dude who has been roped in from another project to do, but he is > busy for the near future. > > If someone knows a thing or two about hg and migration of SVN > repositories with history, as far as I am concerned if they have the > time and interest they can have a crack at the hg migration. Anyone? > > Cheers, > Richard. > > _______________________________________________ > Stackless mailing list > [email protected] > http://www.stackless.com/mailman/listinfo/stackless > -- a lex 13 x http://www.a13x.info _______________________________________________ Stackless mailing list [email protected] http://www.stackless.com/mailman/listinfo/stackless
