From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: masahiroy@kernel.org, jeremie.francois@gmail.com,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH V2] scripts : config : Added example use when run without argument,extend help
Date: Fri, 11 Sep 2020 09:10:41 +0530 [thread overview]
Message-ID: <20200911034037.GA4063@debian> (raw)
In-Reply-To: <508f3917-8b3f-fe38-f6bf-43f5026fc4e2@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1833 bytes --]
On 20:08 Thu 10 Sep 2020, Randy Dunlap wrote:
>On 9/10/20 6:54 PM, Bhaskar Chowdhury wrote:
>> This patch extends the help section by adding an explicit example of use.
>>
>> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
>> ---
>
>Difference between versions goes here.
>
>> scripts/config | 17 +++++++++++++++++
>> 1 file changed, 17 insertions(+)
>>
>> diff --git a/scripts/config b/scripts/config
>> index eee5b7f3a092..d905dccabb94 100755
>> --- a/scripts/config
>> +++ b/scripts/config
>> @@ -45,6 +45,23 @@ make time.
>> By default, $myname will upper-case the given symbol. Use --keep-case to keep
>> the case of all following symbols unchanged.
>>
>> +The concrete example, say, you want to change any particular config,like
>
> config, like
>
>> +GCOV for profiling, you can simply use this command
>
> command.
>
>> +
>> +To enable:
>> +
>> +#scripts/config --enable GCOV_KERNEL && grep GCOV .config
>> +
>> + and the output will be like this:
>> +
>> + CONFIG_GCOV_KERNEL=y
>> +
>> +To disable:
>> +
>> +#scripts/config --disable GCOV_KERNEL && grep GCOV .config
>> +
>> +# CONFIG_GCOV_KERNEL is not set
>> +
>> $myname uses 'CONFIG_' as the default symbol prefix. Set the environment
>> variable CONFIG_ to the prefix to use. Eg.: CONFIG_="FOO_" $myname ...
>> EOL
>>
>
>I don't know why we need this extra help text.
I am not sure I get you ...should have mentioned in the first place, so it
save some of my time ....moreover, I was doing it because I felt it necessary
to let the user of this script to know what/how easily things can be
done.Period.
Look like decision making is badly bugged.
~Bhaskar
>--
>~Randy
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-09-11 3:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 1:54 [PATCH V2] scripts : config : Added example use when run without argument,extend help Bhaskar Chowdhury
2020-09-11 3:08 ` Randy Dunlap
2020-09-11 3:40 ` Bhaskar Chowdhury [this message]
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=20200911034037.GA4063@debian \
--to=unixbhaskar@gmail.com \
--cc=jeremie.francois@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=rdunlap@infradead.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