A hypothetical example would be two different issues whose descriptions
appear to be for different behaviors, but are actually caused by the
same underlying chunk of problematic code being called in different
ways. It could be something trivial like a corner case not being handled.
//Jeff
On 6/10/19 7:57 PM, Mariatta wrote:
Usually we prefer 1 PR per 1 bpo ticket. The smaller the PR is, the
easier it is for us to review, and less likely to cause conflict when
it comes to auto-backporting.
When you say it resolves multiple issues, are these the same issue
reported multiple times?
ᐧ
On Mon, Jun 10, 2019 at 7:52 PM Jeffrey Kintscher
<websur...@surf2c.net <mailto:websur...@surf2c.net>> wrote:
When I create a PR that resolves multiple issues, should I add it
to each issue, or just to one issue and add relevant comments to
the others?
//Jeff
--
-----------------------------------------
From there to here, from here to there,
funny things are everywhere.
-- Theodore Geisel
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
<mailto:python-dev@python.org>
To unsubscribe send an email to python-dev-le...@python.org
<mailto:python-dev-le...@python.org>
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/list/python-dev@python.org/message/74FS2DW2L4MDJXRREAABXYRWNI6INMBA/
--
-----------------------------------------
From there to here, from here to there,
funny things are everywhere.
-- Theodore Geisel
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/list/python-dev@python.org/message/2UWQJWABSSJZD2YRJGMHZQ5WD64HV3UM/
