On Mon, 11 Jan 2016 at 23:52 Oleg Broytman email@example.com wrote:
On Tue, Jan 12, 2016 at 12:25:06AM +0000, Brett Cannon firstname.lastname@example.org wrote:
PEP is still not done, but I have at least fleshed out the parts required to migrate the code-only and web-related repositories:
Buildbot serves a different purpose. This unfinished item is for CI for every submitted pull request while Buildbot is for verifying that the repository on key branches is in a good state.
Tools and commands to move from Mercurial to Git A decision needs to be made on exactly what tooling and what commands involving those tools will be used to convert a Mercurial repository to Git. Currently a suggestion has been made to use https://github.com/frej/fast-export.
My personal experience with fast-export was a bit negative when I tried to convert a repository for a complex project with a number of branches and a lot of tags. I switched to git-remote-hg  and found it much better for my needs. See Comparison .
I'll add it to the list of options.
Oleg Broytman http://phdru.name/ email@example.com Programmers don't die, they just GOSUB without RETURN.
core-workflow mailing list firstname.lastname@example.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