From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Clement Chauplannaz <chauplac@gmail.com>
Cc: linux-kbuild@vger.kernel.org, mmarek@suse.cz, andi@firstfloor.org
Subject: Re: [PATCH 1/2] scripts/config: replace hard-coded script name by a dynamic value
Date: Mon, 20 May 2013 17:57:29 +0200 [thread overview]
Message-ID: <20130520155729.GE3164@free.fr> (raw)
In-Reply-To: <9442eebf0117a0d975ca766ea84efec4ad58c6d0.1368379475.git.chauplac@gmail.com>
Clément, All,
On 2013-05-12 21:08 +0200, Clement Chauplannaz spake thusly:
> The script `config' prints its name in usage() function. It is currently
> hard-coded to value `config'. However, the script may be reused under
> a different name in contexts other than the Linux Kernel.
>
> Replace the hard-coded value `config' by the name of the script at runtime.
>
> Signed-off-by: Clement Chauplannaz <chauplac@gmail.com>
I've applied this in my tree in the branch yem-kconfig-for-next, for
inclusion upstream when the 3.11 merge window opens. Thank you!
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2013-05-20 16:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-12 19:08 [PATCH 0/2] scripts/config: bug fix and improvement Clement Chauplannaz
2013-05-12 19:08 ` [PATCH 1/2] scripts/config: replace hard-coded script name by a dynamic value Clement Chauplannaz
2013-05-12 19:25 ` Andi Kleen
2013-05-12 20:29 ` Yann E. MORIN
2013-05-12 20:54 ` Clément Chauplannaz
2013-05-20 15:57 ` Yann E. MORIN [this message]
2013-05-12 19:08 ` [PATCH 2/2] scripts/config: fix assignment of parameters for short version of --*-after options Clement Chauplannaz
2013-05-20 15:55 ` Yann E. MORIN
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=20130520155729.GE3164@free.fr \
--to=yann.morin.1998@free.fr \
--cc=andi@firstfloor.org \
--cc=chauplac@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.cz \
/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