➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author adelfino
Recipients adelfino, docs@python, fdrake
Date 2018-09-24.19:33:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1537817627.26.0.545547206417.issue34789@psf.upfronthosting.co.za>
In-reply-to
Content 
Admittedly, my Git-fu is not strong, but since the PR was opened against master, and given that the PR as is won't be merged to master, can it still be "backported" to 3.7, 3.6, and 2.7?

Shouldn't I update the PR so it can be merged to master (that won't be backported), and then open a new PR against 3.7 that will be backported to 3.6 and 2.7?
History
Date User Action Args
2018-09-24 19:33:47adelfinosetrecipients: + adelfino, fdrake, docs@python
2018-09-24 19:33:47adelfinosetmessageid: <1537817627.26.0.545547206417.issue34789@psf.upfronthosting.co.za>
2018-09-24 19:33:47adelfinolinkissue34789 messages
2018-09-24 19:33:47adelfinocreate