Messages in this thread | | | From | John Bradford <> | Subject | Re: [RFC] top-level config menu dependencies | Date | Wed, 1 Jan 2003 16:32:23 +0000 (GMT) |
| |
> It has been a long-time tradition that no "real tunable options" are > present in the top level of the kernel config menu. I reckon this has > to do with an inherent limitation of the original config subsystem. > > While converting the way submenus appear in menuconfig depending on > their main, parent config option, I stumbled upon certain subsystems > (such as MTD or IrDA) that should clearly have an on/off switch directly > in the main menu so that one doesn't have to enter the corresponding > submenus to even see if they're enabled or disabled. > > Since the new kernel configurator would have no problems with such > a setup, I'm posting this RFC to get the general opinion on whether > this should be carried on with. I'm willing to create and send in > the patches.
Why not? The config system is changing so much between 2.4 and 2.5 anyway, so any re-organisation like that might as well be done in one go now, rather than during the 2.7 development cycle.
Oh, except that we are in a feature freeze :-), but that doesn't seem to have affected anything else. Infact, I think the current state should be called a
"feature latent-heat-transition-between-melted-and-frozen".
John. - 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/
| |