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 <solip...@pitrou.net> wrote: > On Tue, 20 Dec 2016 02:49:03 +0000 > Brett Cannon <br...@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@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 >
_______________________________________________ core-workflow mailing list core-workflow@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
