Not a solution, but I just wanted to point out the hilarity of the "bro issues" instead of "bpo issues" typo. I've been having a difficult evening and seeing the title in my inbox made me chuckle. Might as well stop and love life's happy little accidents when one has the chance to. :)
On Wed, May 12, 2021 at 10:23 AM Guido van Rossum <gu...@python.org> wrote: > Recently it seems that when a PR linked to a bpo issue is merged, no note > of this event is made in the bpo issue. Look at > https://bugs.python.org/issue43933 for example. There are notes for the > first two merged PRs (25717 and 25719), at > https://bugs.python.org/issue43933#msg392343 and the next message. But I > cannot find a similar note for the third PR, 26054, which is also merged. > > I recall seeing this for other recent issues as well. Did some piece of > automation recently break? (Could it have to do with the master->main move?) > -- > --Guido (mobile) > _______________________________________________ > python-committers mailing list -- python-committers@python.org > To unsubscribe send an email to python-committers-le...@python.org > https://mail.python.org/mailman3/lists/python-committers.python.org/ > Message archived at > https://mail.python.org/archives/list/python-committers@python.org/message/M2Z3WSJ4SGGH2GQ7D5NELAZSD3PECG7Q/ > Code of Conduct: https://www.python.org/psf/codeofconduct/ >
_______________________________________________ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-le...@python.org https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/GDLHBLNRZ3HWSTXVMSUROHSCNHOFUYJM/ Code of Conduct: https://www.python.org/psf/codeofconduct/
