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


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.

Breaking the main tree just because a patch happens to be "good" isn't
a good idea, in general.  Good patchs should not prevent people from
continueing their works.  I think that is thee most important point:
how to ensure that patch checked in would not prevent people from
continuing their works.

-- Gaby


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