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.
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.)
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.
Thanks in advance
Thank-you for submitting your contributor agreement.
Have you had a chance to create your profile on the PSF tracker
http://bugs.python.org/user? If so, please email your "username" &
your "ID #" to me in order for the tracker to show your contributor
agreement submission to the PSF.
On Mon, Oct 24, 2011 at 2:37 AM, Petri Lehtinen <petri(a)digip.org> wrote:
> Attached a signed contributor agreement.
> PSF-Board mailing list
for those of you who also miss the seeing base revision in merge conflict
markers sometimes, I recently saw this post on mercurial-devel:
There is a reason why it is not the default behavior: mercurial collapses
conflict regions when local and other have changed a few lines identically;
this is not possible with 3-way markers.
Petri Lehtinen has been an active contributor for some time, he has been
quite receptive to reviews and we have committed a dozen of his patches.
Do you think it is time to offer him commit rights?
what is the status of the coverity scans? If you go to
and click on "Sign in", you get a maintenance message. For
other projects there is a login screen.
Do we have an official contact person? Is it possible to
have the login reactivated and get access to the scans?