That pushes the third button. I'm nervous that if we go down this path
we will end up with a thicket of modes and a combinatorial explosion
in ruleset complexity, leading immediately to a user configuration
experience that is more complex than necessary, and eventually to an
unmaintainable mess in the rulesfiles.
In order to prevent that happening, I would like to have some recognized
criterion for configuration cases that are so perverse that it is a
net loss to accept the additional complexity of handling them within the
configurator.
A lot of people (including, apparently, you) are saying there are no such
cases. I wonder if you'll change your minds when you have to handle the
overhead yourselves?
Sigh...
-- <a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>"Government is not reason, it is not eloquence, it is force; like fire, a troublesome servant and a fearful master. Never for a moment should it be left to irresponsible action." -- George Washington, in a speech of January 7, 1790 - 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/