I think people should learn to appreciate and live with Linus's style,
because the truth is that Linus probably DOES scale. Linus's strategy
for making his "job" manageable is to make sure that only good patches
get it. So he wants to make sure that the overall structure of Linux is
aesthetic AND EXTENDABLE! However, patch maintainers tend to submit
patches that are only LOCALLY aesthetic (if that), and may have bad
implication for the OVERALL structure.
WE DON'T WANT TO GET CAUGHT IN THE WIN-NT TRAP HERE! Linus has
consistently complained that other people don't think enough before they
submit their patches. Not that that maintainers are stupid, but that
they just do things that "work", and that they don't think about the
implications enough. At least he used to, but it didn't seem to have
much effect. However, it does work though: R. Gooch gave Linus a patch
that Linus actually liked by THINKING about it for while first :)
So, the solution that LInus has proposed is basically that other people
shoulder the work by writing better patches and thinking more about
things in terms of overall structure and code structure, so that Linus
doesn't have to do all the thinking about whether the patches are good
for Linux's overall structure, or whether the changes will cause
problems further down the road.
If people do thinking of the kind, patches will be easier to read, and
they will be smaller, and there will be fewer, and they will accomplish
more. Thus effectively increasing Linus's Mhz, besides distributing
some of the work.
-BenRI
-- http://sdcc13.ucsd.edu/~bredelin- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/