Thanks, Maciej! I created https://github.com/python/core-workflow/issues/12 to track this. If you reply there with your GitHub account I can add you as a collaborator on the project and assign it to you properly.
On Wed, 21 Dec 2016 at 03:05 Maciej Szulik <solt...@gmail.com> wrote: > On Wed, Dec 21, 2016 at 1:14 AM, Nick Coghlan <ncogh...@gmail.com> wrote: > > On 21 December 2016 at 03:46, Brett Cannon <br...@python.org> wrote: > > 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). > > > It's also one of those things where redirecting hg & svn references to the > matching git commits is only a requirement if and when we *do* decide to > shut off the old servers, which would break a *lot* of links in mailing > list archives, Stack Overflow, blog posts, etc. > > Once we get to the point where all remote write access to both servers has > been shut off, a link-preserving, maintenance-reducing solution might be to > bake both the repository data and the corresponding web gateway software > into a pair of Linux container images and then host them wherever is > easiest for the PSF infrastructure team. > > > Not sure how much it's doable, but I can help with that. Once we can > create a commit mapping between > hg, svn and git repo it would be nice to put that in front of svn.p.o and > hg.p.o and redirect to git. > At least it'll teach people that we're on git and this is where they > should look by default. > Yes, that means I'm volunteering to help with that :) > > Maciej > >
_______________________________________________ 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
