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: Bernd Schmidt <bernds at redhat dot com>
- Date: Tue, 10 Jul 2001 11:15:27 +0100 (BST)
- cc: Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
On Mon, 9 Jul 2001, Mark Mitchell wrote:
> We cannot go writing buggy code and then hope that we will have the energy
> to fix it later and somehow expect to get unbuggy code. If we are willing
> to check in buggy code, and not fix it in short order, we have to be
> prepared to have constantly buggy code, and expect to have buggy releases.
That's a strawman - I'm not speaking about allowing buggy check-ins. Revert
those as much as you like. I'm speaking about allowing correct changes to
be checked in, even if they break something, which happens rather often in
my experience. If they expose a different bug, then we have only one bug
in the tree, rather than two, which is IMO preferrable.
The problem is that the buggy code is _already_ checked in, and it'll have
to be fixed somehow. I'm not of the opinion that choosing the convenient
solution of ignoring the problems and reverting patches that expose them
is a good idea.
Bernd