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 in to 3.5, it's their responsibility to
also merge it into the hg.python.org/cpyth
I presume the issue here is that Hg is so complicated that everyone knows a
different subset of the commands and semantics.
I personally don't know what the commands for cherry-picking a revision
would be.
I also don't know exactly what happens when you merge a PR using bitbucket.
(I'm only famil
On 16.08.2015 16:08, Guido van Rossum wrote:
> I presume the issue here is that Hg is so complicated that everyone knows a
> different subset of the commands and semantics.
>
> I personally don't know what the commands for cherry-picking a revision
> would be.
>
> I also don't know exactly what h
On Sun, 16 Aug 2015 00:13:10 -0700, Larry Hastings 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 in to 3.5, it
The 3.5.0 patch flow question also brings up the question of how we
are managing NEWS for 3.5.0 vs 3.5.1. We have some commits that
are going in to both 3.5.0a2 and 3.5.1, and some that are only going
in to 3.5.1. Currently the 3.5.1 NEWS says things are going in to
3.5.0a2, but that's obviously
On Sun, 16 Aug 2015 11:24:32 -0400, "R. David Murray"
wrote:
> On Sun, 16 Aug 2015 00:13:10 -0700, Larry Hastings wrote:
> > 3. After your push request is merged, you pull from
> > bitbucket.com/larry/cpython350 into hg.python.org/cpython and merge
> > into 3.5. In this version I don't
On 8/16/2015 3:13 AM, Larry Hastings 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 in to 3.5, it's their responsibility to
a
On 08/16/2015 07:08 AM, Guido van Rossum wrote:
I presume the issue here is that Hg is so complicated that everyone
knows a different subset of the commands and semantics.
I personally don't know what the commands for cherry-picking a
revision would be.
There are a couple. The command you'd
