[Python-Dev] Heads up: possible double-comments on bpo for commits
Maciej Szulik
soltysh at gmail.com
Thu Feb 2 16:24:37 EST 2017
More information about the Python-Dev mailing list
Thu Feb 2 16:24:37 EST 2017
- Previous message (by thread): [Python-Dev] Heads up: possible double-comments on bpo for commits
- Next message (by thread): [Python-Dev] Heads up: possible double-comments on bpo for commits
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Feb 2, 2017 at 6:01 PM, Victor Stinner <victor.stinner at gmail.com> wrote: > 2017-02-01 18:32 GMT+01:00 Victor Stinner <victor.stinner at gmail.com>: > > To finish with an empty change: > > Information on IRC: > > Known issue: http://psf.upfronthosting.co.za/roundup/meta/issue611 > > "Maciej is working on it" > > Good & thanks! > > I just fixed all the problems mentioned by Victor in this thread, this includes: 1. accidentally closing issues 2. multiple entries in history 3. empty date for gh commit messages (path by Berker - thank you) Ezio confirmed pushing all the changes to bugs.python.org already. I'm very sorry for all the inconvenience caused by previous mistakes. If your issues was closed make sure to verify it was closed properly and re-open if needed. Maciej -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20170202/f9b0c2f0/attachment.html>
- Previous message (by thread): [Python-Dev] Heads up: possible double-comments on bpo for commits
- Next message (by thread): [Python-Dev] Heads up: possible double-comments on bpo for commits
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list