Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Makefile: add help for linux-update-defconfig target
Date: Mon, 6 Apr 2015 23:34:17 +0200	[thread overview]
Message-ID: <20150406233417.68ba7a8d@free-electrons.com> (raw)
In-Reply-To: <55229762.4040302@mind.be>

Arnout,

On Mon, 06 Apr 2015 16:25:38 +0200, Arnout Vandecappelle wrote:

>  Here are the reasons:
> 
> - update-defconfig doesn't exist for all kconfig packages
> 
> - update-defconfig is preferred if it exists (for Linux I certainly see no
> reason to ever use update-config)
> 
> - documenting foo-update-defconfig would perhaps be better, but that's part of a
> bigger change that would completely remove all the specifics. When I did the
> 'make help' patches I started on that, but it turns out to be a bit more work so
> I dropped it in the end.

Hm, well, I'm still not highly convinced on how we handle this
per-package target help text. But anyway, applied, as it isn't that
worse than what we have today.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2015-04-06 21:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-02 19:34 [Buildroot] [PATCH] Makefile: add help for linux-update-defconfig target Yegor Yefremov
2015-04-06 13:16 ` Arnout Vandecappelle
2015-04-06 13:18   ` Thomas Petazzoni
2015-04-06 14:25     ` Arnout Vandecappelle
2015-04-06 21:34       ` Thomas Petazzoni [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=20150406233417.68ba7a8d@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox