Fair enough. Still strange to read this PEP with the explicit caveat of "The author of the PEP doesn't currently plan to write a Process PEP on migration Python development from Mercurial to git."
Georg On 09/15/2015 08:22 PM, Guido van Rossum wrote: > For one, because *I* have been a (moderate) advocate for switching to git and > GitHub. > > On Tue, Sep 15, 2015 at 11:19 AM, Georg Brandl <g.bra...@gmx.net > <mailto:g.bra...@gmx.net>> wrote: > > On 09/15/2015 08:02 PM, Oleg Broytman wrote: > > On Tue, Sep 15, 2015 at 09:46:55AM -0700, Benjamin Peterson > <benja...@python.org <mailto:benja...@python.org>> wrote: > >> This looks like good information, but why is it a PEP? If anything, the > >> devguide was probably be more appropriate. But even that's strange > >> considering we don't use git at the moment. > > > > Exactly because the core team doesn't use git the information doesn't > > belong to the current revision of Developer's Guide. > > And if it doesn't propose to make the core team use git, why is it a PEP? _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
