From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 1/4] Rename the variable "QUIET" to "BR_QUIET" for conformance
Date: Tue, 23 Dec 2014 11:17:26 +0100 [thread overview]
Message-ID: <20141223111726.617588fd@free-electrons.com> (raw)
In-Reply-To: <1419324901-14003-2-git-send-email-fabio.porcedda@gmail.com>
Hello,
On Tue, 23 Dec 2014 09:54:58 +0100, Fabio Porcedda wrote:
> Rename the variable "QUIET" to "BR_QUIET" accordingly to the convention
> that internal variables should be named BR_XXX.
>
> Signed-off-by: Fabio Porcedda <fabio.porcedda@gmail.com>
Do we really want all internal variables to be named BR_* ? Like
HOST_CONFIGURE_OPTS, TARGET_CONFIGURE_OPTS, TARGET_MAKE_ENV and al. ?
I'm not sure we want to do this, do we?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-12-23 10:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 8:54 [Buildroot] [PATCH v5 0/4] Improve silent builds Fabio Porcedda
2014-12-23 8:54 ` [Buildroot] [PATCH v5 1/4] Rename the variable "QUIET" to "BR_QUIET" for conformance Fabio Porcedda
2014-12-23 10:17 ` Thomas Petazzoni [this message]
2014-12-23 10:51 ` Fabio Porcedda
2014-12-28 16:24 ` Fabio Porcedda
2014-12-28 21:57 ` Yann E. MORIN
2014-12-30 10:59 ` Fabio Porcedda
2014-12-30 11:43 ` Fabio Porcedda
2014-12-23 8:54 ` [Buildroot] [PATCH v5 2/4] Makefile: improve detection of make "-s" flag Fabio Porcedda
2014-12-23 8:55 ` [Buildroot] [PATCH v5 3/4] support/download: silence svn if it is a silent build Fabio Porcedda
2014-12-23 8:55 ` [Buildroot] [PATCH v5 4/4] support/download: silence git " Fabio Porcedda
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=20141223111726.617588fd@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