On Jun 4, 2006, at 1:03 PM, Richard Sandiford wrote:
I agree. And I don't think a new gcc by-law is needed here (we
seem so
many of those already). Maintainers can already refuse to review a
"fun
new feature" patch until the submitter has fixed some problem with one
of the submitter's earlier patches (if the maintainer thinks that's
appropriate). I remember at least one case where it has already
happened.
Yes but that is not all the problem because a lot of the time
the maintainer is also the submitter. There is no way to discourage
the behavior of the maintainer on going on to other stuff while there
are known regressions to fix.
-- Pinski
