[Python-Dev] Heads up: possible double-comments on bpo for commits
Victor Stinner
victor.stinner at gmail.com
Thu Feb 2 05:08:14 EST 2017
More information about the Python-Dev mailing list
Thu Feb 2 05:08:14 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 ]
Oh, I noticed another strange thing: The Roundup Robot closed the issue http://bugs.python.org/issue29368 but I don't see any explicit "Close issue #xxx" or "Close #xxx" in the commit message of the two commits. Is it deliberate to close an issue after any commit? Victor 2017-01-31 19:18 GMT+01:00 Brett Cannon <brett at python.org>: > I've activated the webhook for receiving comments on issues when a commit > lands mentioning an issue, so if you see a commit from our hg integration > and another from GitHub, understand that's why (mention issues as "bpo NNNN" > in commit messages if you want to see it in action). If it becomes too much > of a hassle to see the duplicates before we migrate I can turn off the > notifications, but obviously more testing the better. :) > > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/victor.stinner%40gmail.com >
- 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