All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH next] silence awk command display during build
Date: Wed, 15 Sep 2010 00:04:29 +0200	[thread overview]
Message-ID: <20100914220429.688BE15242D@gemini.denx.de> (raw)
In-Reply-To: <201009141525.05345.vapier@gentoo.org>

Dear Mike Frysinger,

In message <201009141525.05345.vapier@gentoo.org> you wrote:
>
> instead of silencing a somewhat complicated command that could break the build 
> system if it goes wrong, use the mechanisms already in place if you want nice 
> & concise output -- the --silent option to make.  i dont see a problem with 
> this output you've quoted in the normal run of things.

I do. It is a change in behaviour and potentially braks a number of
build systems.

Please let's fix this so the previous behaviour is restored.

  parent reply	other threads:[~2010-09-14 22:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-14  1:17 [U-Boot] [PATCH next] silence awk command display during build Kim Phillips
2010-09-14  1:59 ` Mike Frysinger
2010-09-14 18:41   ` Kim Phillips
2010-09-14 19:25     ` Mike Frysinger
2010-09-14 19:48       ` [U-Boot] [PATCH next v2] silence config step commands display during MAKEALL builds Kim Phillips
2010-09-14 19:59         ` Mike Frysinger
2010-09-21 19:47         ` Wolfgang Denk
2010-09-14 22:04       ` Wolfgang Denk [this message]
2010-09-15  2:09         ` [U-Boot] [PATCH next] silence awk command display during build Mike Frysinger
2010-09-15 16:12           ` Kim Phillips
2010-09-15 19:14             ` Mike Frysinger
2010-09-15 19:28               ` Wolfgang Denk
2010-09-15 20:20                 ` Mike Frysinger
2010-09-15 21:25                   ` Wolfgang Denk
2010-09-16  6:20                     ` Mike Frysinger

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=20100914220429.688BE15242D@gemini.denx.de \
    --to=wd@denx.de \
    --cc=u-boot@lists.denx.de \
    /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.