This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: review process
- From: Alexandre Oliva <aoliva at redhat dot com>
- To: Daniel Berlin <dberlin at dberlin dot org>
- Cc: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>, gcc-patches at gcc dot gnu dot org, gcc at gcc dot gnu dot org, Fergus Henderson <fjh at cs dot mu dot OZ dot AU>, Phil Edwards <phil at jaj dot com>, Mark Mitchell <mark at codesourcery dot com>, Gabriel Dos Reis <gdr at integrable-solutions dot net>
- Date: 31 Mar 2003 17:02:42 -0300
- Subject: Re: review process
- Organization: GCC Team, Red Hat
- References: <3E0D6F91-63B2-11D7-BF56-000393575BCC@dberlin.org>
On Mar 31, 2003, Daniel Berlin <dberlin at dberlin dot org> wrote:
>> Why is it so important to tell whether a patch was approved or not?
> Because our goal is to avoid patches being dropped on the floor.
My take is that, if there's a lot of discussion but the proponent of
the patch feels the patch should get reviewed under the light of the
discussion that ensued, an `Ok to install?' message containing a new
copy of the patch, or just the URL to the original posting, should
suffice.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva at {redhat dot com, gcc.gnu.org}
CS PhD student at IC-Unicamp oliva at {lsd dot ic dot unicamp dot br, gnu.org}
Free Software Evangelist Professional serial bug killer