On Thu, Sep 1, 2011 at 4:13 AM, Georg Brandl wrote:
> 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.
>
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
Hi,
On Wed, Aug 31, 2011 at 5:39 PM, Éric Araujo wrote:
> 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.
>
I'm -0 on this. Even if it shouldn't be t
On 8/31/2011 10:39 AM, Éric Araujo 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.
+1 I would have expected this to be the case already. While there is
Ezio prompted me to clarify something: I’m asking for votes more than
code with my message. I can probably change/fix 2) and 3) myself, but
I’d like feedback for 1).
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/m
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.
2) When a bug number (#\d+) is not in the first line of the commit
message, no message is sent. Is there a rea
