A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2016-September/146569.html below:

[Python-Dev] [Python-checkins] cpython (merge 3.5 -> default): Null merge.

[Python-Dev] [Python-checkins] cpython (merge 3.5 -> default): Null merge. [Python-Dev] [Python-checkins] cpython (merge 3.5 -> default): Null merge.Martin Panter vadmium+py at gmail.com
Thu Sep 29 00:38:55 EDT 2016
On 29 September 2016 at 03:04, Terry Reedy <tjreedy at udel.edu> wrote:
> On 9/28/2016 9:57 PM, terry.reedy wrote:
>> https://hg.python.org/cpython/rev/02eb35b79af0
>
> (2nd try) I mistakenly null merged from 3.5 to default.
> Should a now do a proper null merge from 3.5 to 3.6 to default?

Yes, I think 3.5 needs to be merged into 3.6, and the result needs to
be merged into default. I guess they are null merges because the
entries were already present in 3.6b1.

> Should I revert this null merge?

I don’t think there is much point in reverting a null merge, if there
are no actual changes to revert.
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4