[PATCH] README: Alternative configuration commands does not mention make listnewconfig

[PATCH] README: Alternative configuration commands does not mention make listnewconfig

[Regid Ichira]

Applied to the tip of linux.git,
                      VERSION = 3 PATCHLEVEL = 11 SUBLEVEL = 0
Signed-off-by: Regid Ichira <regid23@nt1.in>
---
 README | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/README b/README
index a24ec89..f10c16f 100644
--- a/README
+++ b/README
@@ -228,6 +228,10 @@ CONFIGURING the kernel:
      "make localyesconfig" Similar to localmodconfig, except it will convert
                            all module options to built in (=y) options.
 
+     "make listnewconfig"  Based on the contents of your existing ./.config
+                        file, print all the new config symbols.  One at a
+                        line.
+
    You can find more information on using the Linux kernel config tools
    in Documentation/kbuild/kconfig.txt.
 
-- 
1.8.4.rc3

Re: [PATCH] README: Alternative configuration commands does not mention make listnewconfig

[Randy Dunlap]

On 09/11/13 17:39, Regid Ichira wrote:
> Applied to the tip of linux.git,
>                       VERSION = 3 PATCHLEVEL = 11 SUBLEVEL = 0
> Signed-off-by: Regid Ichira <regid23@nt1.in>
> ---
>  README | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/README b/README
> index a24ec89..f10c16f 100644
> --- a/README
> +++ b/README
> @@ -228,6 +228,10 @@ CONFIGURING the kernel:
>       "make localyesconfig" Similar to localmodconfig, except it will convert
>                             all module options to built in (=y) options.
>  
> +     "make listnewconfig"  Based on the contents of your existing ./.config
> +                        file, print all the new config symbols.  One at a
                                                                 , one per line.

Wow, that's going to be a ton of symbols to read.

And about ./.config, does using O=<build-directory> apply to this (these)
commands?


> +                        line.
> +
>     You can find more information on using the Linux kernel config tools
>     in Documentation/kbuild/kconfig.txt.
>  
> 


-- 
~Randy

Re: [PATCH] README: Alternative configuration commands does not mention make listnewconfig

[Rob Landley]

On 09/11/2013 07:39:19 PM, Regid Ichira wrote:
> Applied to the tip of linux.git,
>                       VERSION = 3 PATCHLEVEL = 11 SUBLEVEL = 0
> Signed-off-by: Regid Ichira <regid23@nt1.in>
> ---
>  README | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/README b/README
> index a24ec89..f10c16f 100644
> --- a/README
> +++ b/README
> @@ -228,6 +228,10 @@ CONFIGURING the kernel:
>       "make localyesconfig" Similar to localmodconfig, except it will  
> convert
>                             all module options to built in (=y)  
> options.
> 
> +     "make listnewconfig"  Based on the contents of your existing  
> ./.config
> +                        file, print all the new config symbols.  One  
> at a
> +                        line.
> +
>     You can find more information on using the Linux kernel config  
> tools
>     in Documentation/kbuild/kconfig.txt.

"make help" does, though. Possibly the README should point people at  
that instead of trying to keep a (third?) copy of this info in sync?

Rob

Re: [PATCH] README: Alternative configuration commands does not mention make listnewconfig

[Regid Ichira]

On Thu, Sep 12, 2013 at 03:18:00AM -0500, Rob Landley wrote:
> On 09/11/2013 07:39:19 PM, Regid Ichira wrote:
> >Applied to the tip of linux.git,
> >                      VERSION = 3 PATCHLEVEL = 11 SUBLEVEL = 0
> >Signed-off-by: Regid Ichira <regid23@nt1.in>
> >---
> > README | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> >diff --git a/README b/README
> >index a24ec89..f10c16f 100644
> >--- a/README
> >+++ b/README
> >@@ -228,6 +228,10 @@ CONFIGURING the kernel:
> >      "make localyesconfig" Similar to localmodconfig, except it
> >will convert
> >                            all module options to built in (=y)
> >options.
> >
> >+     "make listnewconfig"  Based on the contents of your existing
> >./.config
> >+                        file, print all the new config symbols.
> >One at a
> >+                        line.
> >+
> >    You can find more information on using the Linux kernel config
> >tools
> >    in Documentation/kbuild/kconfig.txt.
> 
> "make help" does, though. Possibly the README should point people at
> that instead of trying to keep a (third?) copy of this info in sync?
> 
> Rob


1) If make help is the second copy of this info, and the README is
   the third, where is the first, master, copy?
2) Doesn't the README have slightly more information on each option
   than make help, or that the README info is somewhat better to
   beginners?  Perhaps the README entries should first be combined
   into make help?