From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 0/3] Improve silent builds
Date: Thu, 6 Nov 2014 18:53:30 +0100 [thread overview]
Message-ID: <20141106185330.659d572f@free-electrons.com> (raw)
In-Reply-To: <CAHkwnC-Ds16rDgPAASzLof_xcGgvde_Pni9Vc8Am45gnNT5_PA@mail.gmail.com>
Dear Fabio Porcedda,
On Thu, 6 Nov 2014 18:35:32 +0100, Fabio Porcedda wrote:
> > When I look at patches 2 and 3, I must say I dislike the fact that in
> > one case (svn), silencing is handled in pkg-download.mk when defining
> > the SVN variable, while in the other case (git), it's handled in the
> > git-specific helper script.
>
> I would like to do the same for git but it does not work because:
> git -q clone <url>
> does not work, but
> git clone -q <url>
> works, so adding the "-q" in the script is the only option.
>
> Do you have any better idea?
Yes: handle the svn case in the download helper as well. This way,
we're consistent between svn and git. And maybe wget should be handled
this way as well.
Yann can comment on this on whether my proposal is fine for him.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-11-06 17:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 9:13 [Buildroot] [PATCH v3 0/3] Improve silent builds Fabio Porcedda
2014-11-06 9:13 ` [Buildroot] [PATCH v3 1/3] Makefile: improve detection of make "-s" flag Fabio Porcedda
2014-11-06 9:13 ` [Buildroot] [PATCH v3 2/3] pkg-download: silence the svn download helper if it is a silent build Fabio Porcedda
2014-11-06 9:13 ` [Buildroot] [PATCH v3 3/3] support/download: silence git if it is a silence build Fabio Porcedda
2014-11-06 17:27 ` [Buildroot] [PATCH v3 0/3] Improve silent builds Thomas Petazzoni
2014-11-06 17:35 ` Fabio Porcedda
2014-11-06 17:50 ` Fabio Porcedda
2014-11-06 17:53 ` Thomas Petazzoni [this message]
2014-11-06 18:03 ` Fabio Porcedda
2014-11-11 15:26 ` Fabio Porcedda
2014-11-11 15:37 ` Yann E. MORIN
2014-11-11 15:39 ` Fabio Porcedda
2014-11-24 14:04 ` 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=20141106185330.659d572f@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