horst> Whatever happened to "Do exactly as CML1 does; leave fixes and extensions horst> for later"? If you put the kitchen sink into it, it _won't_ go into the horst> standard kernel.
My opinions: It's important that people who type "make config" or "make oldconfig" or "make menuconfig" or "make xconfig" will continue to have the same experience as they did before. Bug fixes that 90% or 95% of the users agree make things better are okay. Completely new features are okay. "make autoconfigure" is not going to change anyone's experience from CML1. The multiple questions about "what if I want to configure for a different box" indicate to me that Eric's product marketing needs a little work. The product itself is fine, but users are getting the idea that autoconfiguration is part of "make config". I would recommend that Eric talk about "make autoconfigure" rather than the autoprober or autoconfigurator. That makes it more obvious (to me at least) that "make autoconfigure" is a new feature and does not mess with the established semantics of "make config/oldconfig/menuconfig/xconfig". It's fun being retired. I get to pontificate without doing work. :) Michael Elizabeth Chastain <mailto:[EMAIL PROTECTED]> "love without fear" _______________________________________________ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
