From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/4 v9] pkg-download: silence downloads if make is silent
Date: Thu, 1 Jan 2015 22:56:39 +0100 [thread overview]
Message-ID: <20150101225639.2890512b@free-electrons.com> (raw)
In-Reply-To: <8537faa275be0b3bb0aec3da99d7aaf1c56db17c.1420142462.git.yann.morin.1998@free.fr>
Dear Yann E. MORIN,
On Thu, 1 Jan 2015 21:03:52 +0100, Yann E. MORIN wrote:
> From: Fabio Porcedda <fabio.porcedda@gmail.com>
>
> If it is a silent build (make -s -> QUIET=-q) silence all downloads, as
> well as the check-hash. This is done in two ways:
> - redirect stdout to /dev/null
> - pass the -q flag downward to backends
Why do we need to do both?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-01-01 21:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 20:03 [Buildroot] [PATCH 0/4 v9] Improve silent builds (branch yem/fabio/silent) Yann E. MORIN
2015-01-01 20:03 ` [Buildroot] [PATCH 1/4 v9] Makefile: improve detection of make "-s" flag Yann E. MORIN
2015-01-02 15:34 ` Thomas Petazzoni
2015-01-01 20:03 ` [Buildroot] [PATCH 2/4 v9] support/download: support -q in all download backends Yann E. MORIN
2015-01-02 15:01 ` Fabio Porcedda
2015-01-02 15:41 ` Yann E. MORIN
2015-01-01 20:03 ` [Buildroot] [PATCH 3/4 v9] pkg-download: silence downloads if make is silent Yann E. MORIN
2015-01-01 21:56 ` Thomas Petazzoni [this message]
2015-01-01 22:02 ` Yann E. MORIN
2015-01-02 15:36 ` Thomas Petazzoni
2015-01-02 15:41 ` Yann E. MORIN
2015-01-01 20:03 ` [Buildroot] [PATCH 4/4 v9] package/pkg-download: do not hard-code QUIET 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=20150101225639.2890512b@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