Giacomo A. Catenazzi wrote:
quoted text
>> On Friday, 25 of January 2008, Valdis.Kletnieks@vt.edu wrote:
[-mm]
quoted text
>>> should flush out most of the truly stupid mistakes, but those are
>>> usually found and fixed literally within hours.  Anyhow, the proper
>>> time for test compiles is *before* it goes into the git trees at
>>> all - it should have been tested before it gets sent to a
>>> maintainer for inclusion.
> 
> few hours, but a lot of changeset will broke bisect (few doc tell
> us how to continue bisecting on compile errors).
[...]
quoted text
> I only want to raise the problem, to see if it is possible to improve
> testing environment without affecting the development of Linux.

How often is "bisectability" being broken already before merge in
subsystem trees, and how often only in the context of the merge result?
(Probably impossible to answer because nobody has the data.)

Much of the former type of breakage (if we really have such breakage)
could probably be found in mostly automated ways and by volunteer
testers, by regularly testing the subsystem trees.
-- 
Stefan Richter
-=====-==--- ---= ==-=-
http://arcgraph.de/sr/
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/