>>> On 17.12.10 at 03:03, Arnaud Lacombe <lacombar@xxxxxxxxx> wrote:
> hum, I just thought of something. Instead of adding more complexity to
> the menu children, why would {,m,n,q}conf descend to these submenus at
> first. they should just ignore all the childs if the parent is not
> meant to be visible and go to the next node on the same level. When I
> close the front door of my house, I do expect people to stop right
> there, not continue to check any door I may have left open inside.
Isn't that what's happening? I don't think the problem is with the
frontends - it's the backend that writes out settings of options it
didn't before (and shouldn't).
Jan
--
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
