On Jan 31, 2018, at 16:03, R. David Murray <rdmur...@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 n...@python.org -- [] _______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
