[python-committers] 3.7.0b1 status (original) (raw)
Ned Deily nad at python.org
Wed Jan 31 16:14:00 EST 2018
- Previous message (by thread): [python-committers] 3.7.0b1 status
- Next message (by thread): [python-committers] 3.7.0b1 status
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Jan 31, 2018, at 16:03, R. David Murray <rdmurray at bitdance.com> wrote:
Hmm. I merge something and put on the backport 3.6 label and just merged that...and I have no idea if the 3.7 merge was before or after the b1 cutoff. Is there some way to get git to tell us which commits are possible candidates for cherry picking after the branch is created so that we don't miss any? Otherwise I fear we may end up with some bug fixes that get in to 3.8 and 3.6 but not 3.7.
Hang tight, I'm working on that right at this moment :) Almost ready!
-- Ned Deily nad at python.org -- []
- Previous message (by thread): [python-committers] 3.7.0b1 status
- Next message (by thread): [python-committers] 3.7.0b1 status
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]