From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] help: add a way to document targets declared in local.mk/external.mk
Date: Tue, 8 Mar 2016 22:19:55 +0100 [thread overview]
Message-ID: <20160308221955.4567b005@free-electrons.com> (raw)
In-Reply-To: <20160308220221.0a5088d0@free-electrons.com>
Hello,
On Tue, 8 Mar 2016 22:02:21 +0100, Thomas Petazzoni wrote:
> > Looks good to me, except that I don't like the name 'LOCAL'. I'd prefer e.g.
> > ADDITIONAL.
>
> Wouldn't EXTERNAL_HELP be even better, suggesting that its main
> use-case is for BR2_EXTERNAL ?
My suggestion obviously doesn't work if we want to use this for
internal packages, as PATCH 2/2 is doing.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-03-08 21:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 14:37 [Buildroot] [PATCH 1/2] help: add a way to document targets declared in local.mk/external.mk Jérôme Pouiller
2015-11-18 14:37 ` [Buildroot] [PATCH 2/2] help: relocate help messages specific to one package Jérôme Pouiller
2015-11-18 14:49 ` Thomas Petazzoni
2015-11-19 10:44 ` Jérôme Pouiller
2015-11-29 20:39 ` Arnout Vandecappelle
2016-03-08 20:58 ` Arnout Vandecappelle
2015-11-29 20:26 ` [Buildroot] [PATCH 1/2] help: add a way to document targets declared in local.mk/external.mk Yann E. MORIN
2015-11-30 12:04 ` Jérôme Pouiller
2015-11-30 22:22 ` Arnout Vandecappelle
2016-03-08 20:54 ` Arnout Vandecappelle
2016-03-08 21:02 ` Thomas Petazzoni
2016-03-08 21:19 ` Thomas Petazzoni [this message]
2016-03-08 21:21 ` Arnout Vandecappelle
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=20160308221955.4567b005@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 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.