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 at codesourcery dot com
- Subject: Re: Beyond GCC 3.0: Summing Up
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- Date: Mon, 9 Jul 01 21:21:38 EDT
- Cc: gcc at gcc dot gnu dot org
I agree -- as long as someone is actively working on a patch. If
nobody is working on a patch, then by what mechanism are we going to
ensure that we fix the problem before the release?
The same way we "ensure" that *any* problem is fixed before the release:
by listing it as a bug and trying to persuade somebody to fix it. If
nobody does, then reverting the original patch is one possibility, but,
at least in cases where the breakage is minor, delaying reversion to
a time when it's the only choice may be worthwhile. Of course, this is
not viable for large patches which cannot be easily reverted well after
they are applied.