This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: review process (was: C++ PATCH: Unify name lookup 2/n)
- From: Phil Edwards <phil at jaj dot com>
- To: Daniel Berlin <dberlin at dberlin dot org>
- Cc: Fergus Henderson <fjh at cs dot mu dot OZ dot AU>, Mark Mitchell <mark at codesourcery dot com>, Gabriel Dos Reis <gdr at integrable-solutions dot net>, gcc-patches at gcc dot gnu dot org
- Date: Mon, 31 Mar 2003 01:43:45 -0500
- Subject: Re: review process (was: C++ PATCH: Unify name lookup 2/n)
- References: <20030331041419.GA4687@ceres.cs.mu.oz.au> <7A485D03-633E-11D7-8FBD-000393575BCC@dberlin.org>
On Mon, Mar 31, 2003 at 01:03:22AM -0500, Daniel Berlin wrote:
>
> If our problem is really in reviewing significant patches (ie i'm
> assuming we aren't dropping 3 line patches on the floor, and that
> people just approve these while reading through email regularly), we
> could track those that aren't approved in a day through bugzilla.
I was going to ask you about this... would patches then be also treated
as bug reports? Or would it be a seperate "interface", e.g., patchzilla?
> I can even work up some code so that requests approved this way get an
> email generated to gcc-patches stating that the patch was approved.
That would be nice.
Phil
--
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace. We seek
not your counsel, nor your arms. Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen. - Samuel Adams