On Wed, Aug 31, 2011 at 5:39 PM, Éric Araujo <merwok@netwok.org> wrote:

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.

I'm -0 on this. Even if it shouldn't be too difficult to implement I'm not sure it's worth doing it, since it's not something that happens often enough and when it does you usually want to explain something more to the second issue anyway.  Moreover fixes should be related to a single issue.
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.)

From a quick look at the code I don't see any obvious reason why this shouldn't work, if it really doesn't I guess it can be fixed.  (I prefer to always write the issue number at beginning of the line though.)
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.

It would be useful for the devguide repo too, now that we have a 'devguide' component (and possibly for 'benchmarks' too, as you suggested on #python-dev).
Thanks in advance

Best Regards,
Ezio Melotti