[core-workflow] Help needed: best way to convert hg repos to git?

Ryan Gonzalez rymg19 at gmail.com
Sun Feb 7 17:50:29 EST 2016

Well, hg-git might not work...

I cloned the CPython repo. I then ran `hg gexport`, which converts the
repository to Git. Took three hours, but it worked!

However, actually attempted to push the result to a Git repo failed
miserably. After five hours, Mercurial ran out of memory in the "adding
objects" stage. And I have 6 GB of RAM!

Right now, I'm trying to see if I can work around it. This may not work
out, though.

On Sat, Feb 6, 2016 at 10:37 AM, Ryan Gonzalez <rymg19 at gmail.com> wrote:

> I'll try hg-git!
> On February 5, 2016 7:57:15 PM CST, Brett Cannon <brett at python.org> wrote:
>> https://www.python.org/dev/peps/pep-0512/#define-commands-to-move-a-mercurial-repository-to-git
>> There appear to be multiple ways to convert hg repos to git, but no clear
>> winner. It would be great if some one/people took on the task of evaluating
>> the tools available out there by converting the cpython repo and seeing
>> which one has the best results.
>> ------------------------------
>> core-workflow mailing list
>> core-workflow at python.org
>> https://mail.python.org/mailman/listinfo/core-workflow
>> This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct
> --
> Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.

[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160207/b190b7a8/attachment.html>

More information about the core-workflow mailing list