On Wed, 4 June 2008 13:42:38 -0700, Tim Bird wrote: > Adrian Bunk wrote: > > I might be wrong, but although monitoring the size makes a lot of sense > > I don't believe "fully automate the testing ... and send notifications" > > will work. > > "fully automate" was sloppy wording on my part. "automate enough > to not be a burden to maintain" is what I should have said. Even that blows. People all too easily forget about the end-to-end principle. If you want a system that scales well, you have to push as much work as possible to the ends and do as little as possible in the center. Applies here as well as in networking. If CELF funds 20 people to do such tests, they may be able to cope today. But the stream of developers keeps swelling, so even those 20 won't be able to cope long-term. Instead we have to enable everyone in the stream of developers to easily check for themselves. If then stream keeps swelling, the amount of bloat-checking swells along. What scales well is the "make check*" targets in the source. Some even claim it scales too well and attracts too many clueless janitors. I'd be happy if we ever get into the same trouble with bloat checking. ;) Jörn -- Das Aufregende am Schreiben ist es, eine Ordnung zu schaffen, wo vorher keine existiert hat. -- Doris Lessing -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html