[core-workflow] GitHub migration update for 2016-12-19
Brett Cannon
brett at python.org
Tue Dec 20 12:46:52 EST 2016
Long-term yes, but I'm under time pressure here and with no one helping me
deal with this problem I went with the easiest solution that I knew
wouldn't break unexpectedly (hence the simplification for mapping svn
changesets to svn.python.org and not keeping all the code around to map to
hg.python.org).
On Mon, 19 Dec 2016 at 23:49 Antoine Pitrou <solipsis at pitrou.net> wrote:
> On Tue, 20 Dec 2016 02:49:03 +0000
> Brett Cannon <brett at python.org> wrote:
> > The biggest update is I have updated the code for hg.python.org/lookup.
> > Once the hg repo is read-only I will generate a final JSON file
> containing
> > every commit and then have the new code and data uploaded. If you want to
> > look at the modified code and double-check my work then please look at
> > https://gist.github.com/brettcannon/f8d97c92b0df264cd4db008ffd32daf9.
>
> I thought you were going to redirect hg changeset references to github,
> so that we don't have to maintain hg.p.o indefinitely.
>
> Ditto for SVN revision references (which currently are redirected to
> hg.p.o, not svn.p.o).
>
> Regards
>
> Antoine.
>
>
> _______________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20161220/fd5516a1/attachment.html>
More information about the core-workflow
mailing list