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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 13 Sep 2013 00:26:36 +0300
From:	Regid Ichira <regid23@....in>
To:	Rob Landley <rob@...dley.net>
Cc:	"Steven Mr. Procrastinator Rostedt" <rostedt@...dmis.org>,
	Jiri Kosina <jkosina@...e.cz>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] README: Alternative configuration commands does not
 mention make listnewconfig

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@....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?
--
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/