[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20070724054943.GA12946@uranus.ravnborg.org>
Date: Tue, 24 Jul 2007 07:49:43 +0200
From: Sam Ravnborg <sam@...nborg.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Al Boldi <a1426z@...ab.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Kconfig: Remove top level menu "Code maturity level options"
On Mon, Jul 23, 2007 at 04:58:13PM -0700, Andrew Morton wrote:
> On Sat, 21 Jul 2007 06:58:28 +0300
> Al Boldi <a1426z@...ab.com> wrote:
>
> >
> > This patch removes the top level menu "Code maturity level options", and
> > moves its options into menu "General setup".
> >
> > This makes Kconfig less cluttered and easier to setup.
> >
> >
> > Cc: Andrew Morton <akpm@...l.org>
> > Signed-off-by: Al Boldi <a1426z@...ab.com>
> >
> > ---
> > --- a/init/Kconfig 2007-07-09 06:38:47.000000000 +0300
> > +++ b/init/Kconfig 2007-07-21 06:42:06.000000000 +0300
> > @@ -7,7 +7,7 @@ config DEFCONFIG_LIST
> > default "/boot/config-$UNAME_RELEASE"
> > default "arch/$ARCH/defconfig"
> >
> > -menu "Code maturity level options"
> > +menu "General setup"
> >
> > config EXPERIMENTAL
> > bool "Prompt for development and/or incomplete code/drivers"
> > @@ -61,9 +61,6 @@ config INIT_ENV_ARG_LIMIT
> > Maximum of each of the number of arguments and environment
> > variables passed to init from the kernel command line.
> >
> > -endmenu
> > -
> > -menu "General setup"
> >
> > config LOCALVERSION
> > string "Local version - append to kernel release"
>
> OK (IMO). The "Code maturity level options" menu only has a single
> entry, and I doubt if it will grow more entries any time soon. It
> makes sense to kill it and to move its sole entry into "General setup".
Agreed. These should be a reason for a menu and a single entry is not enough.
Acked-by: Sam Ravnborg <sam@...nborg.org>
Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists