[python-committers] Three wishes for Mercurial-Roundup integration
Georg Brandl
g.brandl at gmx.net
Wed Aug 31 20:13:25 CEST 2011
More information about the python-committers mailing list
Wed Aug 31 20:13:25 CEST 2011
- Previous message: [python-committers] Three wishes for Mercurial-Roundup integration
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Am 31.08.2011 16:39, schrieb Éric Araujo: > Hi, > > 1) When a commit message references more than one bug (with text > matching #\d+), only the first gets a message for the changeset. I > would like all referenced bugs to get a message. +1. Just make sure that only issues that should be closed are closed (i.e. if the commit message is """Close #1234: better fix than proposed in #5678""", #1234 should be closed, and #5678 get a reference). > 2) When a bug number (#\d+) is not in the first line of the commit > message, no message is sent. Is there a reason for this or is it a bug? > (Note: I’m not sure about this one, I may misremember.) I can't imagine why that would be. So if it is indeed the case, it's a bug. > 3) To let us track the backport of changesets from cpython/packaging to > distutils2, I would like the script to look at changesets in the > distutils2 repo and send messages to Roundup when a bug number is detected. Sure. Should be a simple [hooks] entry. Georg
- Previous message: [python-committers] Three wishes for Mercurial-Roundup integration
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list