On 13.09.2009 18:07, Gregory P. Smith wrote:
On Sun, Sep 13, 2009 at 8:54 AM, Matthias Klose wrote:
On 06.04.2009 00:33, Matthias Klose wrote:
While looking at the diffs between the 261 release tags and the 26 branch,
I
noticed many items in Misc/NEWS appearing in the 2.6.1 or even 2.6
sectio
On Sun, Sep 13, 2009 at 13:30, Benjamin Peterson wrote:
> 2009/9/13 Brett Cannon :
>> issue6844 wants to stop a warning from being raised when someone
>> accesses a 'message' attribute on an exception when it is set by the
>> user (currently any usage of the 'message' attribute raises a
>> warning
Le dimanche 13 septembre 2009 à 13:27 -0700, Brett Cannon a écrit :
>
> Right, which is why only the first line would be used. All the other
> usual detail can be there, just do it on another line.
But if that line is longer than 80 characters, your $EDITOR may split it
automatically and it'll br
2009/9/13 Brett Cannon :
> issue6844 wants to stop a warning from being raised when someone
> accesses a 'message' attribute on an exception when it is set by the
> user (currently any usage of the 'message' attribute raises a
> warning). To do this properly is going to require some state flag on
>
On Sun, Sep 13, 2009 at 13:26, Antoine Pitrou wrote:
> Le dimanche 13 septembre 2009 à 13:15 -0700, Brett Cannon a écrit :
>>
>> Or simply take the first line of each commit? I mean why do we enter
>> it twice? If we have a commit that is unimportant we could come up
>> with some convention to mak
issue6844 wants to stop a warning from being raised when someone
accesses a 'message' attribute on an exception when it is set by the
user (currently any usage of the 'message' attribute raises a
warning). To do this properly is going to require some state flag on
BaseException's struct. But I don'
On Sun, 13 Sep 2009 at 13:15, Brett Cannon wrote:
On Sun, Sep 13, 2009 at 09:07, Gregory P. Smith wrote:
Thanks. ??One reason this happens is that our NEWS file is very
difficult to navigate. ??svnmerge rarely works on it because the
context is often different in the branch file but figuring ou
Le dimanche 13 septembre 2009 à 13:15 -0700, Brett Cannon a écrit :
>
> Or simply take the first line of each commit? I mean why do we enter
> it twice? If we have a commit that is unimportant we could come up
> with some convention to make it as such or simply have the comment
> start with a blan
On Sun, Sep 13, 2009 at 09:07, Gregory P. Smith wrote:
> On Sun, Sep 13, 2009 at 8:54 AM, Matthias Klose wrote:
>> On 06.04.2009 00:33, Matthias Klose wrote:
>>>
>>> While looking at the diffs between the 261 release tags and the 26 branch,
>>> I
>>> noticed many items in Misc/NEWS appearing in t
On Sun, Sep 13, 2009 at 8:54 AM, Matthias Klose wrote:
> On 06.04.2009 00:33, Matthias Klose wrote:
>>
>> While looking at the diffs between the 261 release tags and the 26 branch,
>> I
>> noticed many items in Misc/NEWS appearing in the 2.6.1 or even 2.6
>> sections.
>> I moved all of these to 2.
On 06.04.2009 00:33, Matthias Klose wrote:
While looking at the diffs between the 261 release tags and the 26 branch, I
noticed many items in Misc/NEWS appearing in the 2.6.1 or even 2.6 sections.
I moved all of these to 2.6.2, after checking some of them, and found all of the
checked ones be bac
11 matches
Mail list logo
