On 1/31/2018 8:04 PM, Ned Deily wrote:
In the cpython repo, there is now a 3.7 branch. Starting now, all PRs
destined for 3.7.0 should get cherry-picked from master to the 3.7
branch or just pushed to 3.7 if only applicable there. New features
should continue to be pushed to the master branch fo
>
> Should a patch for 3.6 be cherry-picked directly from master or from 3.7?
> Does it matter? With hg, double forward merges had to be done linearly, as
> from 3.6 to 3.7 and thence from 3.7 to 3.8 (master).
cherry_picker.py and miss-islington will backport from master to newest
branch first.
On 1/31/2018 7:03 PM, Barry Warsaw wrote:
$ git worktree add ../3.7 3.7 # ftw!
f:\dev\3x> git worktree add ../37 3.7
fatal: invalid reference: 3.7
f:\dev\3x> git worktree add -b 3.7 ../37 3.7
fatal: Not a valid object name: '3.7'.
# However
f:\dev\3x> git checkout 3.7
# 'exposes' the existi
