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

In article <20150615003717.2599.82804@psf.io>, senthil.kumaran <python-checkins@python.org> wrote:
https://hg.python.org/cpython/rev/9a0c5ffe7420 changeset: 96605:9a0c5ffe7420 parent: 96603:47a566d6ee2a parent: 96604:3ded282f9615 user: Senthil Kumaran <senthil@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@acm.org

On Sunday, June 14, 2015 at 6:43 PM, Ned Deily wrote:
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. Oh! Missed that. Sorry, for the trouble. I will update my local branches and follow the process.
3.4 -> 3.5 3.5 -> default Thank you! Senthil
participants (2)
-
Ned Deily
-
Senthil Kumaran