public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Al Boldi <a1426z@gawab.com>
Cc: linux-kernel@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH] Kconfig:  Remove top level menu "Code maturity level options"
Date: Mon, 23 Jul 2007 16:58:13 -0700	[thread overview]
Message-ID: <20070723165813.20848a85.akpm@linux-foundation.org> (raw)
In-Reply-To: <200707210658.28241.a1426z@gawab.com>

On Sat, 21 Jul 2007 06:58:28 +0300
Al Boldi <a1426z@gawab.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@osdl.org>
> Signed-off-by: Al Boldi <a1426z@gawab.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".

  reply	other threads:[~2007-07-23 23:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-21  3:58 [PATCH] Kconfig: Remove top level menu "Code maturity level options" Al Boldi
2007-07-23 23:58 ` Andrew Morton [this message]
2007-07-24  5:49   ` Sam Ravnborg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070723165813.20848a85.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=a1426z@gawab.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox