Author fdrake
Recipients adelfino, docs@python, fdrake
Date 2018-09-24.20:51:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1537822281.28.0.545547206417.issue34789@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2018-09-24 20:51:21fdrakesetrecipients: + fdrake, docs@python, adelfino
2018-09-24 20:51:21fdrakesetmessageid: <1537822281.28.0.545547206417.issue34789@psf.upfronthosting.co.za>
2018-09-24 20:51:21fdrakelinkissue34789 messages
2018-09-24 20:51:21fdrakecreate