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

Xavier Morel python-dev at masklinn.net
Sun Aug 16 16:30:00 CEST 2015

On 2015-08-16, at 16:08 , Guido van Rossum <guido at 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.


> I also don't know exactly what happens when you merge a PR using bitbucket. (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.)

Same thing IIRC, I don't think there's a way to "squash" a merge via the web interface in either.

> BTW When I go to https://bitbucket.org/larry/cpython350 the first thing I see (in a very big bold font) is "This is Python version 3.6.0 alpha 1". What's going on here? It doesn't inspire confidence.

It's the rendered content of the README file at the root of the repository, same as github.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20150816/3035cc42/attachment.html>

More information about the Python-Dev mailing list