<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Mon, 11 Jan 2016 at 23:52 Oleg Broytman <<a href="mailto:phd@phdru.name">phd@phdru.name</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi!<br>
<br>
On Tue, Jan 12, 2016 at 12:25:06AM +0000, Brett Cannon <<a href="mailto:brett@python.org" target="_blank">brett@python.org</a>> wrote:<br>
> PEP is still not done, but I have at least fleshed out the parts required<br>
> to migrate the code-only and web-related repositories:<br>
> <a href="https://github.com/brettcannon/github-transition-pep/blob/master/pep-NNNN.rst" rel="noreferrer" target="_blank">https://github.com/brettcannon/github-transition-pep/blob/master/pep-NNNN.rst</a> .<br>
<br>
> Continuous integration per pull request<br>
> XXX <a href="https://travis-ci.org/" rel="noreferrer" target="_blank">https://travis-ci.org/</a> <a href="https://codeship.com/" rel="noreferrer" target="_blank">https://codeship.com/</a> <a href="https://circleci.com/" rel="noreferrer" target="_blank">https://circleci.com/</a><br>
<br>
   No buildbot?<br></blockquote><div><br></div><div>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.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
> Tools and commands to move from Mercurial to Git<br>
> A decision needs to be made on exactly what tooling and what commands<br>
> involving those tools will be used to convert a Mercurial repository to<br>
> Git. Currently a suggestion has been made to use<br>
> <a href="https://github.com/frej/fast-export" rel="noreferrer" target="_blank">https://github.com/frej/fast-export</a>.<br>
<br>
   My personal experience with fast-export was a bit negative when I<br>
tried to convert a repository for a complex project with a number of<br>
branches and a lot of tags. I switched to git-remote-hg [1] and found it<br>
much better for my needs. See Comparison [2].<br>
<br>
1. <a href="https://github.com/felipec/git-remote-hg" rel="noreferrer" target="_blank">https://github.com/felipec/git-remote-hg</a><br>
2. <a href="https://github.com/felipec/git/wiki/Comparison-of-git-remote-hg-alternatives" rel="noreferrer" target="_blank">https://github.com/felipec/git/wiki/Comparison-of-git-remote-hg-alternatives</a></blockquote><div><br></div><div>I'll add it to the list of options.</div><div><br></div><div>-Brett</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
Oleg.<br>
--<br>
     Oleg Broytman            <a href="http://phdru.name/" rel="noreferrer" target="_blank">http://phdru.name/</a>            <a href="mailto:phd@phdru.name" target="_blank">phd@phdru.name</a><br>
           Programmers don't die, they just GOSUB without RETURN.<br>
_______________________________________________<br>
core-workflow mailing list<br>
<a href="mailto:core-workflow@python.org" target="_blank">core-workflow@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/core-workflow" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/core-workflow</a><br>
This list is governed by the PSF Code of Conduct: <a href="https://www.python.org/psf/codeofconduct" rel="noreferrer" target="_blank">https://www.python.org/psf/codeofconduct</a><br>
</blockquote></div></div>