This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: review process

From: Daniel Berlin <dberlin at dberlin dot org>
To: Alexandre Oliva <aoliva at redhat dot com>
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: Mon, 31 Mar 2003 14:52:02 -0500
Subject: Re: review process

On Monday, March 31, 2003, at 02:32 PM, Alexandre Oliva wrote:

On Mar 31, 2003, Daniel Berlin <dberlin at dberlin dot org> wrote:
Obviously, i don't need something in some strict format, I just need
to be able to determine that a given message containing patch was
approved (or approved with changes, etc).  Thus, simply saying that
approval messages should contain a line starting with "approved".
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. There are plenty of times where there is a lot of discussion, and updates, but then it just sits there waiting for final approval/rejection. This is "dropped on the floor".

Follow-Ups:
- Re: review process
  - From: Alexandre Oliva

References:
- Re: review process
  - From: Alexandre Oliva

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]