On 29 November 2014 at 03:34, Demian Brecht <demianbre...@gmail.com> wrote: > On Tue, Nov 25, 2014 at 6:52 AM, Brett Cannon <br...@python.org> wrote: >> >> I suspect if we make sure we add Bitbucket and GitHub login support to the >> issue tracker then that would help go a fair distance to helping with the >> GitHub pull of reach (and if we make it so people can simply paste in their >> fork's URL into the issue tracker and we simply grab a new patch for review >> that would go even farther). > > Chiming in horribly late, so hopefully this hasn't already been > mentioned (I've only loosely been following this thread). > > In addition to the login support (I'm not sold on how much that would > help the reach), I think it would be really beneficial to have some > documentation on either emulating git-style workflow in hg or > detailing a git fork workflow while working on multiple patches > concurrently and keeping master in sync with hg default (or perhaps > even both).
As far as I'm aware, the easiest way to do that by using git-remote-hg to treat the CPython Mercurial repository as a git remote (although I've never tried it myself). Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ 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
