Oh yes, one issue of missing bpo-xxx is that bots don't report merged commits into the bpo. I like using the bpo issue to track backports:
https://bugs.python.org/issue31902 It was just a general remark, it's fine for these commits. Someone can add them manually to the bpo if you want. Victor Le mer. 12 sept. 2018 à 17:56, Victor Stinner <vstin...@redhat.com> a écrit : > > Hi Benjamin, > > https://github.com/python/cpython/commit/d13e59c1b512069d90efe7ee9b613d3913e79c56 > > Le mer. 12 sept. 2018 à 17:19, Benjamin Peterson <benja...@python.org> a > écrit : > > (Just checking) Is there something wrong with this message besides the <-- > > comment? > > Since the commit is described as a follow-up of > 90fc8980bbcc5c7dcced3627fe172b0bfd193a3b, maybe it could also include > "bpo-31902: " prefix in it's title. Just to ease following where the > change comes from. > > IMHO the main complain of Serhiy was the giant <!-- ... --> comment > ;-) I agree that this one has to go, and hopefully it's already fixed. > We are now good! > > Victor _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
