> On Nov 29, 2014, at 9:01 PM, Donald Stufft <donald at stufft.io> wrote: > >> >> The PEP should also cover providing clear instructions for setting up git-remote-hg with the remaining Mercurial repos (most notably CPython), as well as documenting a supported workflow for generating patches based on the existing CPython GitHub mirror. >> >> > > I can add this. I’ve never actually tried using git-remote-hg with CPython > itself because I’ve made it segfault on other Mercurial repositories and I > never figured out why so I just generally fight my way through using Mercurial > on projects that themselves use Mercurial. I will absolutely test to see if > git-remote-hg works with CPython and I can document using that to contribute to > CPython. I’m not sure it needs to be part of the PEP or not? Feels like > something that would be better inside the devguide itself but I’m not opposed > to putting it both locations. Nevermind. I’m not going to add this because git-remote-hg is busted with the latest version of Mercurial and I don’t think it’s really needed for this PEP (though would be good for the devguide at some point). --- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20141129/cb982bbc/attachment.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4