Message326285
The existing PR can be re-targeted to merge to a maintenance branch (I'd be inclined to merge manually, myself, but will have to check the current devguide to make sure that's still allowed).
A new PR can be made for the non-documentation fix for master.
My thought is that a PR is more about the patch than about the workflow; a different patch can be handled in a separate PR, and review & discussion are used to determine which PR should be applied where. |
|
Date |
User |
Action |
Args |
2018-09-24 20:51:21 | fdrake | set | recipients:
+ fdrake, docs@python, adelfino |
2018-09-24 20:51:21 | fdrake | set | messageid: <1537822281.28.0.545547206417.issue34789@psf.upfronthosting.co.za> |
2018-09-24 20:51:21 | fdrake | link | issue34789 messages |
2018-09-24 20:51:21 | fdrake | create | |
|