A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2010-July/101970.html below:

[Python-Dev] python-checkins replies

[Python-Dev] python-checkins replies [Python-Dev] python-checkins repliesanatoly techtonik techtonik at gmail.com
Thu Jul 15 11:10:32 CEST 2010
On Tue, Jul 13, 2010 at 2:42 AM, Michael Foord
<fuzzyman at voidspace.org.uk> wrote:
>>>
>>> Given how high traffic python-checkins is I don't consider that a
>>> reasonable place to send follow-up and nor do I consider it the
>>> responsibility of committers to monitor it. As you said earlier this
>>> *isn't* in our standard dev procedures and nor do I think it should be.
>>> If you can't find an email address then either python-comitters or
>>> python-dev would be a better place to send feedback.
>>
>> Maybe reply-to on the checkin messages could be set to python-dev. Not
>> sure if that's a mailman feature, though.
>
> I think this would be a good idea. It would be nice to have on-topic traffic
> here. :-)

+1 FWIW. It is a good practice to make code reviews public. It teaches
people the proper ways and encourages to participate in reviews.
-- 
anatoly t.
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4