Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] support/download: further silence the git helper
Date: Mon, 5 Jan 2015 18:40:55 +0100	[thread overview]
Message-ID: <20150105174054.GA5077@free.fr> (raw)
In-Reply-To: <CAHkwnC9Ri41gSQ5Oh+Y=XCRcvGbC0S1MSGY5W-AOpg8qLaCM+g@mail.gmail.com>

Fabio, All,

On 2015-01-05 12:35 +0100, Fabio Porcedda spake thusly:
> On Sun, Jan 4, 2015 at 7:10 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > We expresely call printf in the git helper, calls which were not
> > addresed in the previous silent-build patchset.
> >
> > Just redirect stdout to oblivion when being silent.
> >
> > Reported-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> > Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> > Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> > ---
> >  support/download/git | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/support/download/git b/support/download/git
> > index 7f1801f..73cbc0f 100755
> > --- a/support/download/git
> > +++ b/support/download/git
> > @@ -14,7 +14,7 @@ set -e
> >  verbose=-v
> >  while getopts :q OPT; do
> >      case "${OPT}" in
> > -    q)  verbose=-q;;
> > +    q)  verbose=-q; exec >/dev/null;;
> 
> As general rule It's best to use "&&" instead of ";" so any error can
> be caught,

That is really not necessary, because the backend scripts are all
'set -e', so they exit on the first error that occurs.

Besides, even if they were not 'set -e', then the '&&' construct would
not catch the error at all, and the script would continue without
redirecting.

Furthermore, in that case, we're doing two things:
  - set a variable
  - redirect stdout to /dev/null

If either were to fail, you would have a hell of a bigger problem:
  - unable to set a variable: big problem in the shell
  - not able to redirect: /dev/null does not exist, or you do not have
    the rights to write to it.

In either case, this would be a really, *really* big problem, which I
doubt we should care about. ;-)

> otherwise is:
> Acked-by: Fabio Porcedda <fabio.porcedda@gmail.com>
> Tested-by: Fabio Porcedda <fabio.porcedda@gmail.com>

Thanks!

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2015-01-05 17:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-04 18:10 [Buildroot] [PATCH] support/download: further silence the git helper Yann E. MORIN
2015-01-05 11:35 ` Fabio Porcedda
2015-01-05 17:40   ` Yann E. MORIN [this message]
2015-01-05 14:15 ` Thomas Petazzoni

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=20150105174054.GA5077@free.fr \
    --to=yann.morin.1998@free.fr \
    --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