On 2015-08-16, at 16:08 , Guido van Rossum gu...@python.org 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.
graft
I also
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
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
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 happens
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
On Sun, Aug 16, 2015 at 7:08 AM, Guido van Rossum gu...@python.org wrote:
(I'm only familiar with the GitHub PR flow, and I don't like its behavior,
which seems to always create an extra merge revision for what I consider as
logically a single commit.)
For whatever it's worth, this is a
