I've found that hggit works very well - I used it to migrate my work project to github and still use it to avoid having to deal with git. (My intent is to keep using it for Python as well.)
Is the plan to migrate the entire history or just master? Top-posted from my Windows Phone -----Original Message----- From: "R. David Murray" <rdmur...@bitdance.com> Sent: 1/5/2016 7:34 To: "python-committers" <python-committers@python.org> Subject: Re: [python-committers] We will be moving to GitHub (hopefully) in2016 On Mon, 04 Jan 2016 18:18:02 +0000, Brett Cannon <br...@python.org> wrote: > On Mon, 4 Jan 2016 at 09:50 Eli Bendersky <eli...@gmail.com> wrote: > > > > I have to admit that I'm not a big expert on Mercurial --> Git converters > > and the way I maintain this mirror may not be the best approach, so I > > encourage you folks to find a VCS guru to look into this for the "real" > > transition. > > > > That will be one of the early steps of the transition. :) Maybe The PSF could fund Eric Raymond to do this? He's got beyond-the-basics tooling, and a fair bit of experience converting large projects. He might even be able to clean up the older (svn) history along the way, although that might be too much to hope for ;) (Oh, and let me mention this while I'm thinking about it: we're going to have to do some extra work to make the hash links work in the bug tracker, since I don't think there's any a priori way to distinguish between hg hashes and git hashes.) --David _______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers
_______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers
