I do support (and use) the strategy of killing bugs by ripping out whole (buggy)
sections of code and replacing them with better/simpler/cleaner/not-inlined-
by-hand-all-over versions. However, perhaps more attention should be paid to
documentation/commenting, so that we get fewer patches with "I think I satisfy
everybody's expectations but I don't know what they are" disclaimers (I've seen
that so often on patches that are supposed to *fix* 2.0.30, *correctly*!), and
so that we can find the 2.1.recent crashing problems once and for all by giving
the code to a bunch of grade schoolers. If you start commenting now, someone
will probably be able to get the support of a few schools by the time fall
semester starts...
Keith (only kidding about the use of underage labor)
P.S. I looked through fs/inode.c, and was amused to discover a comment which
begins: `The "new" scheduling primitives (new as of 0.97 or so)'...
brings back memories of sticking distributions with 0.94(?) onto
floppies...