> I see the confusion. I think Martin meant more about open issues that
> required discussion, not simply issues that had a patch ready to go.
I actually think it is perfectly fine to point out that specific issues
are need committer action on this list. This is what the list is there for.
Waitin
I am aware my email has gone out multiple times. My phone kept saying that
it was not sent, so I kept trying to force it to send. Sorry about the extra
emails.
On Fri, Apr 16, 2010 at 10:50, Brett Cannon wrote:
> Yes, we have different opinions. My personal take is to wait a week before
> you em
Yes, we have different opinions. My personal take is to wait a week before
you email python-dev if there has been no activity. That is enough time for
people interested in the patch to get to it as we all have different
schedules. Any faster and it feels like noise on the list to me.
Brett (from h
Yes, we have different opinions. My personal take is to wait a week before
you email python-dev if there has been no activity. That is enough time for
people interested in the patch to get to it as we all have different
schedules. Any faster and it feels like noise on the list to me.
Brett (from h
Yes, we have different opinions. My personal take is to wait a week before
you email python-dev if there has been no activity. That is enough time for
people interested in the patch to get to it as we all have different
schedules. Any faster and it feels like noise on the list to me.
Brett (from h
Yes, we have different opinions. My personal take is to wait a week before
you email python-dev if there has been no activity. That is enough time for
people interested in the patch to get to it as we all have different
schedules. Any faster and it feels like noise on the list to me.
Brett (from h
On Apr 14, 2010, at 5:19 PM, Brett Cannon wrote:
> I see the confusion. I think Martin meant more about open issues that
> required discussion, not simply issues that had a patch ready to go.
Ach. I hit 'send' too soon. I also wanted to say: it seemed quite clear to me
that Martin specifical
On Apr 14, 2010, at 5:19 PM, Brett Cannon wrote:
> I see the confusion. I think Martin meant more about open issues that
> required discussion, not simply issues that had a patch ready to go.
I'm curious - if one isn't supposed to ping the mailing list every time, how
does one ask the tracker "
On Wed, Apr 14, 2010 at 13:41, Chris Jerdonek wrote:
> On Wed, Apr 14, 2010 at 1:32 PM, Brett Cannon wrote:
> > There is no need to email python-dev about individual patches just to get
> > them looked at. There is a mailing list that we all subscribe to that
> send
> > an email on all new issues
On Wed, Apr 14, 2010 at 1:32 PM, Brett Cannon wrote:
> There is no need to email python-dev about individual patches just to get
> them looked at. There is a mailing list that we all subscribe to that send
> an email on all new issues and another one on every change to any issue. You
> should only
On Tue, Apr 13, 2010 at 20:54, Chris Jerdonek wrote:
> Here is another patch for review:
>
> http://bugs.python.org/issue8370
>
> This is a trivial fix to the 2.6 and 2.7 documentation.
>
>
There is no need to email python-dev about individual patches just to get
them looked at. There is a mailing
Here is another patch for review:
http://bugs.python.org/issue8370
This is a trivial fix to the 2.6 and 2.7 documentation.
Thanks,
--Chris
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
12 matches
Mail list logo
