RetroSearch Browse

Tue Jun 1 00:10:22 EDT 2004 · http://mail.python.org/pipermail/python-dev/2004-June/045073.html

"Martin v. L?wis" <martin at v.loewis.de>:

> It is not surprising the patches haven't seen any
> comments: We get way more patches than we can handle
> these days. If you want to help, please review patches
> of other people, and recommend adaption or rejection.

I doubt I'm the only one who assumed that anything but
a change suggestion would be counterproductive; that it
would just be adding a "me too" that slowed down the 
person who could actually check the patch in.

If reviews from anyone are welcome, it wouldn't hurt 
to mention that a few more places.  Ideally, it would
be in the:

(1)  boilerplate that you see when looking at a patch
(2)  boilerplate at the top of a list of patches
<URL: http://sourceforge.net/tracker/?group_id=5470&atid=305470 >
(3)  developer documentation.  (I can sort of find it in 
<URL: http://www.python.org/dev/dev_intro.html#helping-out >, 
but didn't see it until I was already looking specifically 
for information on patch reviews.)
(4)  pre-announce for a new alpha release.

-jJ

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

Showing content from http://mail.python.org/pipermail/python-dev/2004-June/045073.html below:

[Python-Dev] RE: Python-Dev Digest, Vol 10, Issue 52