All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Makefile: help: BR2_DEFCONFIG for defconfig must be on command line
Date: Sat, 28 Jul 2018 23:22:20 +0200	[thread overview]
Message-ID: <20180728232220.4f75ee21@windsurf> (raw)
In-Reply-To: <20180722213445.29358-1-arnout@mind.be>

Hello,

On Sun, 22 Jul 2018 23:34:45 +0200, Arnout Vandecappelle
(Essensium/Mind) wrote:
> The help text says that BR2_DEFCONFIG will be used as input, but a
> BR2_DEFCONFIG specified in the existing .config file will *not* be
> used. So say explicitly that it must be specified on the command line.
> Note that both "BR2_DEFCONFIG=... make defconfig" and
> "make defconfig BR2_DEFCONFIG=..." will work.
> 
> While we're at it, add a semicolon to separate the two statements.
> 
> Note that this overflows the help text beyond 80 characters, but that
> is already the case in many other lines.
> 
> Reported-by: "aissen" on IRC

aissen is Anisse Astier, so I've fixed that up when applying.

> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> ---
>  Makefile | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-07-28 21:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-22 21:34 [Buildroot] [PATCH] Makefile: help: BR2_DEFCONFIG for defconfig must be on command line Arnout Vandecappelle
2018-07-28 21:22 ` Thomas Petazzoni [this message]
2018-08-23 20:03 ` Peter Korsgaard

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=20180728232220.4f75ee21@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.