On 10/6/2014 1:15 AM, Nick Coghlan wrote:
On 6 October 2014 13:17, Larry Hastings wrote:
I also didn't want to add another RC and slip the release--Matthias said he
wanted to ship 3.4.2 with Ubuntu 14.10, but with their release only about
two weeks away I didn't want to stress them out any mor
On 6 October 2014 13:17, Larry Hastings wrote:
>
> I also didn't want to add another RC and slip the release--Matthias said he
> wanted to ship 3.4.2 with Ubuntu 14.10, but with their release only about
> two weeks away I didn't want to stress them out any more than necessary.
> (One might say, "U
On 6 October 2014 07:22, Terry Reedy wrote:
> On 10/5/2014 3:39 PM, Terry Reedy wrote:
>>
>> I responded on the issue,
>> and will say more privately.
>
> I wrote him and tried to communicate three ideas.
> 1. Closing issues and responding to new messages, while important, are
> subsidiary to the
On 10/05/2014 07:11 AM, R. David Murray wrote:
Larry, saw your discussion on IRC with Georg about what to cherry pick
into the release clone before issuing final. IMO you shouldn't cherry
pick anything, since I believe there have been *zero* issues opened that
said that the RC was broken.
3.4.
On Sun, Oct 5, 2014 at 6:34 PM, Raymond Hettinger <
raymond.hettin...@gmail.com> wrote:
> I'm not at all into banning, but it would be nice if Mark's interest
> could be channelled into something useful.
>
Yes, given that he is reasonable on emails. So requesting him to not just
prod/churn issues
On Oct 5, 2014, at 1:44 PM, Antoine Pitrou wrote:
> Le 05/10/2014 21:02, Terry Reedy a écrit :
>>
>> If you are annoyed, lets discuss specifics and see if we can agree on
>> refined guidelines to give him. It could even be "leave Benjamin's
>> issues alone".
>
> I'd like him to stop blindly
Le 05/10/2014 23:22, Terry Reedy a écrit :
> On 10/5/2014 3:39 PM, Terry Reedy wrote:
>> I responded on the issue,
>> and will say more privately.
>
> I wrote him and tried to communicate three ideas.
> 1. Closing issues and responding to new messages, while important, are
> subsidiary to the pr
On 10/05/2014 11:01 PM, Ned Deily wrote:
> In article ,
> Georg Brandl wrote:
>> On 10/05/2014 09:36 PM, Ned Deily wrote:
>> > To me, the main issue is that the noise is not just directed at python
>> > committers but also to the python users who have submitted those issues or
>> > otherwise foll
On 10/5/2014 3:39 PM, Terry Reedy wrote:
I responded on the issue,
and will say more privately.
I wrote him and tried to communicate three ideas.
1. Closing issues and responding to new messages, while important, are
subsidiary to the primary goal of improving Python.
2. We would prefer more
In article ,
Georg Brandl wrote:
> On 10/05/2014 09:36 PM, Ned Deily wrote:
> > To me, the main issue is that the noise is not just directed at python
> > committers but also to the python users who have submitted those issues or
> > otherwise following them (via nosy or otherwise). I think the
Le 05/10/2014 21:02, Terry Reedy a écrit :
>
> If you are annoyed, lets discuss specifics and see if we can agree on
> refined guidelines to give him. It could even be "leave Benjamin's
> issues alone".
I'd like him to stop blindly pinging issues without trying to
investigate them. I routinel
On 10/05/2014 09:36 PM, Ned Deily wrote:
> On Oct 5, 2014, at 12:24 , R. David Murray wrote:
>>
>> It is certainly true that I for one ignore anything with his name on it,
>> because most of the time it is noise and it isn't worth the effort to
>> figure out which ones aren't noise.
>
> To me,
Le 05/10/2014 21:36, Ned Deily a écrit :
> On Oct 5, 2014, at 12:24 , R. David Murray wrote:
>>
>> It is certainly true that I for one ignore anything with his name on it,
>> because most of the time it is noise and it isn't worth the effort
>> to figure out which ones aren't noise.
>
> To me, t
On 10/5/2014 2:47 PM, Benjamin Peterson wrote:
On Sun, Oct 5, 2014, at 14:42, Serhiy Storchaka wrote:
On 05.10.14 21:15, Benjamin Peterson wrote:
"BreamoreBoy" is back on tracker touching hundreds of issues without
adding any new information. This is certainly not the first time. Can we
ban him
On 10/5/2014 2:15 PM, Benjamin Peterson wrote:
"BreamoreBoy" is back on tracker touching hundreds of issues without
adding any new information. This is certainly not the first time. Can we
ban him?
Can we? Of course, but that is a rare last resort. Should we? No.
I have closed several issues
On Oct 5, 2014, at 12:24 , R. David Murray wrote:
>
> It is certainly true that I for one ignore anything with his name on it,
> because most of the time it is noise and it isn't worth the effort
> to figure out which ones aren't noise.
To me, the main issue is that the noise is not just directe
On Sun, 05 Oct 2014 14:47:06 -0400, Benjamin Peterson
wrote:
> On Sun, Oct 5, 2014, at 14:42, Serhiy Storchaka wrote:
> > On 05.10.14 21:15, Benjamin Peterson wrote:
> > > "BreamoreBoy" is back on tracker touching hundreds of issues without
> > > adding any new information. This is certainly not
On Sun, Oct 5, 2014, at 14:42, Serhiy Storchaka wrote:
> On 05.10.14 21:15, Benjamin Peterson wrote:
> > "BreamoreBoy" is back on tracker touching hundreds of issues without
> > adding any new information. This is certainly not the first time. Can we
> > ban him?
>
> I think it would be enough jus
On 05.10.14 21:15, Benjamin Peterson wrote:
"BreamoreBoy" is back on tracker touching hundreds of issues without
adding any new information. This is certainly not the first time. Can we
ban him?
I think it would be enough just to say him stop. He is not malicious.
Actually there was few cases
"BreamoreBoy" is back on tracker touching hundreds of issues without
adding any new information. This is certainly not the first time. Can we
ban him?
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo
Le 05/10/2014 16:11, R. David Murray a écrit :
> Larry, saw your discussion on IRC with Georg about what to cherry pick
> into the release clone before issuing final. IMO you shouldn't cherry
> pick anything, since I believe there have been *zero* issues opened that
> said that the RC was broken.
Larry, saw your discussion on IRC with Georg about what to cherry pick
into the release clone before issuing final. IMO you shouldn't cherry
pick anything, since I believe there have been *zero* issues opened that
said that the RC was broken. IMO the only differences between the last
RC and final
22 matches
Mail list logo
