Hi,
On 02/09/2011 19.53, Éric Araujo wrote:
Le 31/08/2011 20:13, Georg Brandl a écrit :
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
Le 12/10/2011 19:24, Georg Brandl a écrit :
> OK; should be fixed now.
It is, thanks!
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers
Am 12.10.2011 18:10, schrieb Éric Araujo:
> Le 06/10/2011 19:25, Georg Brandl a écrit :
>> Did you get a "sent email to roundup" message on push?
>
> Just pushed to the distutils2 repo:
>
> remote: adding changesets
> remote: adding manifests
> remote: adding file changes
> remote: added 6 change
Le 06/10/2011 19:25, Georg Brandl a écrit :
> Did you get a "sent email to roundup" message on push?
Just pushed to the distutils2 repo:
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 6 changesets with 13 changes to 8 files
remote: Traceback (most rec
Le 06/10/2011 19:29, Antoine Pitrou a écrit :
> Le jeudi 06 octobre 2011 à 16:34 +0200, Éric Araujo a écrit :
>> This changeset: http://hg.python.org/distutils2/rev/3749fcae0dce
>> failed to update this report: http://bugs.python.org/issue1
> Are you sure? From here it seems to have worked fine
Le jeudi 06 octobre 2011 à 16:34 +0200, Éric Araujo a écrit :
> Le 03/09/2011 08:42, Georg Brandl a écrit :
> > Am 02.09.2011 18:53, schrieb Éric Araujo:
> 3) To let us track the backport of changesets from cpython/packaging to
> distutils2, I would like the script to look at changesets i
On 10/06/11 16:34, Éric Araujo wrote:
> Le 03/09/2011 08:42, Georg Brandl a écrit :
>> Am 02.09.2011 18:53, schrieb Éric Araujo:
> 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
Le 03/09/2011 08:42, Georg Brandl a écrit :
> Am 02.09.2011 18:53, schrieb Éric Araujo:
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 num
Am 02.09.2011 18:53, schrieb Éric Araujo:
>>> 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 [h
On Sat, Sep 3, 2011 at 2:53 AM, Éric Araujo wrote:
> Le 31/08/2011 20:13, Georg Brandl a écrit :
>>> 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.
Le 31/08/2011 20:13, Georg Brandl a écrit :
>> 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
On Wed, Aug 31, 2011 at 8:44 PM, Ezio Melotti wrote:
>
>
>> 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 co
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
18 matches
Mail list logo
