Re: [python-committers] [Python-Dev] How are we merging forward from the Bitbucket 3.5 repo?

2015-08-24 Thread Larry Hastings
On 08/16/2015 08:24 AM, R. David Murray wrote: On Sun, 16 Aug 2015 00:13:10 -0700, Larry Hastings la...@hastings.org wrote: Can we pick one approach and stick with it? Pretty-please? Pick one Larry, you are the RM :) Okay. Unsurprisingly, I pick what I called option 3 before. It's

Re: [python-committers] [Python-Dev] How are we merging forward from the Bitbucket 3.5 repo?

2015-08-16 Thread R. David Murray
On Sun, 16 Aug 2015 11:24:32 -0400, R. David Murray rdmur...@bitdance.com wrote: On Sun, 16 Aug 2015 00:13:10 -0700, Larry Hastings la...@hastings.org wrote: 3. After your push request is merged, you pull from bitbucket.com/larry/cpython350 into hg.python.org/cpython and merge

Re: [python-committers] [Python-Dev] How are we merging forward from the Bitbucket 3.5 repo?

2015-08-16 Thread R. David Murray
On Sun, 16 Aug 2015 00:13:10 -0700, Larry Hastings la...@hastings.org wrote: So far I've accepted two pull requests into bitbucket.com/larry/cpython350 in the 3.5 branch, what will become 3.5.0rc2. As usual, it's the contributor's responsibility to merge forward; if their checkin goes