This is the mail archive of the gcc@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]

Re: Beyond GCC 3.0: Summing Up


On Jul 10, 2001, Gabriel Dos Reis <Gabriel.Dos-Reis@cmla.ens-cachan.fr> wrote:

> Bernd Schmidt <bernds@redhat.com> writes:
> | 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.

> I think the proposal isn't to forget completely the good patch.
> As I understand it, it is about 

>    1) taking it out temporarily
>    2) fix the latent bug
>    3) then recheck-in the good patch.

This is a longish recipe to get a number of such patches forgotten,
unless the proponent of the patch has enough energy (and time) to get
the other problem exposed by the patch fixed.  I don't think it's fair
to place the burden on the proponent of the patch, who has already
fixed one bug, after all.  At the very least, the maintainer of the
component in which the latent bug existed should share part of the
burden, and, IMO, so should anybody else involved in the development
of GCC and interested on the platform on which the bug shows up.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me


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