2011/1/18 Michal Marek <mmarek@xxxxxxx>: > On 17.1.2011 23:50, Yann E. MORIN wrote: >> Filip, All, >> >> On Monday 17 January 2011 23:39:17 Filip Honckiewicz wrote: >>> It helped me a lot and now it's clear. Your example shows everything. >>> In kconfig-language.txt there is: >>> "This is similar to the simple config entry above, but it also gives >>> a hint to front ends, that all suboptions should be displayed as a >>> separate list of options." and this "suboptions" fool me that if >>> there're suboptions than there has to be ending of menuconfig entry;) >> >> Maybe expressing this in a more understandable way, such as: >> >> The menuconfig scope ends with the last config options that depends >> on that menuconfig entry. > > Then such sentence would have to be added to "config" as well. Or just > point people to the Menu structure chapter. > > Michal > I agree with Michal. It makes no sense. But maybe remove "suboptions" and change whole sentence to something like this: "This is similar to the simple config entry above, but it also gives a hint to front ends, that all other options that depends on this entry should be displayed as a separate list of options." and maybe add Michal's example to "Menu structure" chapter to show this little difference between config and menuconfig. Or maybe not;) Sorry for my english. Filip -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
