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 serhiy.storchaka
Recipients belopolsky, musically_ut, ned.deily, serhiy.storchaka
Date 2017-07-02.18:07:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Are there any guides re: backporting commits?
> Just to confirm verify that I'm going about it right; I’m planning on cherry-picking relevant commits back to branch 3.5, 3.6, resolving the merge conflicts, and then opening two separate PRs for them with `bpo-30822` in their titles.

All right. See . You can cherry-pick manually or using which adds correct prefix to commit message and helps to create a pull request.
Date User Action Args
2017-07-02 18:07:16serhiy.storchakasetrecipients: + serhiy.storchaka, belopolsky, ned.deily, musically_ut
2017-07-02 18:07:16serhiy.storchakasetmessageid: <>
2017-07-02 18:07:16serhiy.storchakalinkissue30822 messages
2017-07-02 18:07:16serhiy.storchakacreate