On Sat, Sep 8, 2012 at 10:29 PM, Chris Jerdonek
wrote:
> On hg.python.org, it seems like the entries on the "log" page don't
> always link to the corresponding revision:
>
> http://hg.python.org/cpython/shortlog
>
> This seems to happen whenever the revision description begins with
> text that res
On hg.python.org, it seems like the entries on the "log" page don't
always link to the corresponding revision:
http://hg.python.org/cpython/shortlog
This seems to happen whenever the revision description begins with
text that results in a link to something else (e.g. an issue number),
for example
On Sep 8, 2012, at 8:16 PM, Nick Coghlan wrote:
> On Sun, Sep 9, 2012 at 6:18 AM, Chris Jerdonek
> wrote:
>> This raises a related question. Where should we file issues for
>> Python-controlled things that are outside the scope of the cpython
>> repository (or the devguide) and that are not is
On Sun, Sep 9, 2012 at 6:18 AM, Chris Jerdonek wrote:
> This raises a related question. Where should we file issues for
> Python-controlled things that are outside the scope of the cpython
> repository (or the devguide) and that are not issues with the tracker
> (which has its own tracker -- the
On Thu, Sep 6, 2012 at 10:26 AM, R. David Murray wrote:
> On Thu, 06 Sep 2012 13:15:14 -0400, Terry Reedy wrote:
>> My understanding is that the tracker is for the cpython repository at
>> hg.python.org and my impression is that web code is elsewhere.
>
> That is true. However, the appearance an
Am 08.09.2012 16:52, schrieb Antoine Pitrou:
> On Fri, 7 Sep 2012 02:27:25 +0200 (CEST)
> christian.heimes wrote:
>> http://hg.python.org/cpython/rev/8cd6acffbcb9
>> changeset: 78871:8cd6acffbcb9
>> branch: 2.7
>> parent: 78867:2587aeb616b6
>> user:Christian Heimes
>> date:
Am 08.09.2012 11:35, schrieb Stefan Krah:
> That sounds good in principle. I'm only worried that for casual readers
> of either the commit messages or the tracker issues the importance of
> the Coverity tool might be overstated.
>
> After all, 99.99% of issues are either found by developers themse
On Sat, Sep 8, 2012 at 6:41 AM, wrote:
>
> Zitat von Stefan Krah :
>
> After all, 99.99% of issues are either found by developers themselves or
>> by gcc, Visual Studio, Valgrind, etc. It just occurred to me that for
>> example
>> we don't credit other tools in commit messages.
>>
>
> I agree th
On Fri, 7 Sep 2012 02:27:25 +0200 (CEST)
christian.heimes wrote:
> http://hg.python.org/cpython/rev/8cd6acffbcb9
> changeset: 78871:8cd6acffbcb9
> branch: 2.7
> parent: 78867:2587aeb616b6
> user:Christian Heimes
> date:Fri Sep 07 00:55:33 2012 +0200
> summary:
> Iss
On Sat, Sep 8, 2012 at 9:17 PM, Stefan Krah wrote:
> Petri Lehtinen wrote:
>> > ("715365") does not exist.
>>
>> Is this related to the Coverity ID being mentioned in
>> http://bugs.python.org/issue15868 ?
>
> Must be. I used the pattern # twice in the commit message:
>
> http://hg.python.org/cpy
Petri Lehtinen wrote:
> > ("715365") does not exist.
>
> Is this related to the Coverity ID being mentioned in
> http://bugs.python.org/issue15868 ?
Must be. I used the pattern # twice in the commit message:
http://hg.python.org/cpython/rev/df663603e67a
So let's avoid that in the future.
Ste
Python tracker wrote:
>
>
> The node specified by the designator in the subject of your message
> ("715365") does not exist.
>
> Subject was: "[issue715365]"
Is this related to the Coverity ID being mentioned in
http://bugs.python.org/issue15868 ?
___
Zitat von Stefan Krah :
After all, 99.99% of issues are either found by developers themselves or
by gcc, Visual Studio, Valgrind, etc. It just occurred to me that for example
we don't credit other tools in commit messages.
I agree that Coverity doesn't need to be mentioned in commit message.
W
Christian Heimes wrote:
> IMHO it makes sense to define a workflow how we are going to handle
> Coverity issues. Each coverity issue has an identifier and can have
> information like an external reference and an action. I've seen that you
> have started to create bugs in our tracker. How about we
The node specified by the designator in the subject of your message
("715365") does not exist.
Subject was: "[issue715365]"
Mail Gateway Help
=
Incoming messages are examined for multiple parts:
. In a multipart/mixed message or part, each subpart is extracted and
examined
15 matches
Mail list logo
