Serhiy Storchaka added the comment: > 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30822> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
