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

Showing content from https://mail.python.org/pipermail/python-dev/2015-June/140502.html below:

[Python-Dev] cpython (merge 3.4 -> default): null merge with 3.4

• Previous message (by thread): [Python-Dev] What were the complaints of binary code programmers that not accept Assembly?
• Next message (by thread): [Python-Dev] cpython (merge 3.4 -> default): null merge with 3.4
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

In article <20150615003717.2599.82804 at psf.io>,
 senthil.kumaran <python-checkins at python.org> wrote:
> https://hg.python.org/cpython/rev/9a0c5ffe7420
> changeset:   96605:9a0c5ffe7420
> parent:      96603:47a566d6ee2a
> parent:      96604:3ded282f9615
> user:        Senthil Kumaran <senthil at uthcode.com>
> date:        Sun Jun 14 17:37:09 2015 -0700
> summary:
>   null merge with 3.4
> 
> Back porting changeset db302b88fdb6 to 3.4 branch, which fixed multiple 
> documentation typos.
> 
> Related Issues:
> #issue21528
> #issue24453
> 
> files:

Senthil,

There is now an active 3.5 branch, so the correct current order of 
merging is:

3.4 -> 3.5
3.5 -> default

I've checked in a couple of null merges to try to fix things.

-- 
 Ned Deily,
 nad at acm.org

• Previous message (by thread): [Python-Dev] What were the complaints of binary code programmers that not accept Assembly?
• Next message (by thread): [Python-Dev] cpython (merge 3.4 -> default): null merge with 3.4
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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