Message297523
> 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 https://docs.python.org/devguide/committing.html#backporting-changes-to-an-older-version . You can cherry-pick manually or using cherry_picker.py which adds correct prefix to commit message and helps to create a pull request. |
|
Date |
User |
Action |
Args |
2017-07-02 18:07:16 | serhiy.storchaka | set | recipients:
+ serhiy.storchaka, belopolsky, ned.deily, musically_ut |
2017-07-02 18:07:16 | serhiy.storchaka | set | messageid: <1499018836.46.0.590593958116.issue30822@psf.upfronthosting.co.za> |
2017-07-02 18:07:16 | serhiy.storchaka | link | issue30822 messages |
2017-07-02 18:07:16 | serhiy.storchaka | create | |
|