From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] RFC: Concise Build Output
Date: Tue, 29 Jan 2008 11:06:34 +0100 [thread overview]
Message-ID: <200801291106.35349.sr@denx.de> (raw)
In-Reply-To: <47992BFE.5000906@gmail.com>
On Friday 25 January 2008, gvb.uboot wrote:
> > I think this is a good change myself. The biggest reason is that it
> > makes the default output terse instead of verbose. I'd hazard to
> > wager that most developers don't use 'make -s', MAKEALL, or anything
> > else to trim the output (I certainly don't). By making the default
> > output terse, with errors and warning visually distinct from progress
> > indication, in increases the likelyhood that warnings will actually
> > get seen and fixed (because more people will notice it).
> >
> > I say make this change.
> >
> > Cheers,
> > g.
>
> Plus my 2 cents if this is a voting matter.
Add my 2 cents too. :)
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2008-01-29 10:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 22:11 [U-Boot-Users] RFC: Concise Build Output Jon Loeliger
2008-01-23 22:33 ` Jean-Christophe PLAGNIOL-VILLARD
2008-01-24 0:41 ` Wolfgang Denk
2008-01-24 22:08 ` Scott Wood
2008-01-24 23:18 ` Wolfgang Denk
2008-01-24 23:26 ` Scott Wood
2008-01-24 23:21 ` Grant Likely
2008-01-25 0:23 ` gvb.uboot
2008-01-29 10:06 ` Stefan Roese [this message]
2008-01-25 17:39 ` Jon Loeliger
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=200801291106.35349.sr@denx.de \
--to=sr@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.