Well, I think that some changes need some wider testing anyway.
They may be correct from the author's point of view and even from the knowledge
and point of view of the maintainer who takes them into his tree. That's
because no one knows everything and it'll always be like this.
Still, with the current process such "suspicious" changes go in as parts of
large series of commits and need to be "rediscovered" by the affected testers
with the help of bisection. Moreover, many changes of this kind may go in from
many different sources at the same time and that's really problematic.
In fact, so many changes go in at a time during a merge window, that we often
can't really say which of them causes the breakage observed by testers and
bisection, that IMO should really be a last-resort tool, is used on the main
debugging techinque.
--
