From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] RFC: Concise Build Output
Date: Thu, 24 Jan 2008 17:26:42 -0600 [thread overview]
Message-ID: <47991EB2.7040306@freescale.com> (raw)
In-Reply-To: <20080124231842.349F72430B@gemini.denx.de>
Wolfgang Denk wrote:
> In message <47990C67.1010104@freescale.com> you wrote:
>> Wolfgang Denk wrote:
>>> So my question is: which problem are you trying to solve that is not
>>> already solved by "make -s" or "MAKEALL"? I don't really see the need
>>> for a solution between no output and full output. YMMV, of course.
>> It's nice to have a progress meter of what's currently being compiled,
>> without so much noise that warnings are missed.
>
> Hm... you don't need a progress meter, you need a faster machine ;-)
Either that or Ritalin. :-)
-Scott
next prev parent reply other threads:[~2008-01-24 23:26 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 [this message]
2008-01-24 23:21 ` Grant Likely
2008-01-25 0:23 ` gvb.uboot
2008-01-29 10:06 ` Stefan Roese
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=47991EB2.7040306@freescale.com \
--to=scottwood@freescale.com \
--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.