This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Beyond GCC 3.0: Summing Up
- To: Mark Mitchell <mark at codesourcery dot com>
- Subject: Re: Beyond GCC 3.0: Summing Up
- From: Jonathan Larmour <jlarmour at redhat dot com>
- Date: Tue, 10 Jul 2001 21:44:03 +0100
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Organization: Red Hat UK Ltd.
- References: <13880000.994795563@warlock.codesourcery.com>
Mark Mitchell wrote:
>
> We went around this block before. They don't have to do it themselves;
> they just have to ask someone to do it for them. An easy way to do this
> is to check in the change to CVS, on a branch, and point people at the
> branch. If we can't get volunteers to check out and test the branch,
> then something is badly wrong.
People do complain about unreviewed patches already. This implies to me
that we don't have the spare developer capacity to deal with such a
workload. After all, it's not enough for someone to just have access to the
hardware, and then saying "it didn't build"; instead they're the ones who
will have to do a lot of the debugging if it doesn't work, which is much
more effort than reviewing a patch.
All I'm suggesting is flexibility if an individual's circumstances do not
permit such wide testing. Having a "policy" implies losing such
flexibility.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062