From: gvb.uboot <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] RFC: Concise Build Output
Date: Thu, 24 Jan 2008 19:23:26 -0500 [thread overview]
Message-ID: <47992BFE.5000906@gmail.com> (raw)
In-Reply-To: <fa686aa40801241521m393015f5oc0e5a3b9550683e6@mail.gmail.com>
Grant Likely wrote:
> On 1/23/08, Wolfgang Denk <wd@denx.de> wrote:
>> Dear Jon,
>>
>> in message <E1JHnoD-0004we-IN@jdl.com> you wrote:
>>> In the spirit of the Linux and Git build systems,
>>> I have a modified U-Boot build system that supports
>>> a much more concise output! One of the primary
>>> motivations for this style of output is that it
>>> will very readily highlight build issues and problems
>>> as your build progresses. The original, complete
>>> build output is obtainable by simply supplying "V=1"
>>> on the make invocation in exactly the same way as
>>> both Linux and Git do today.
> <snip>
>> 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.
>>
>> Hope I didn't frustrate you - I still appreciate the effort.
>
> Hey Jon, Wolfgang;
>
> 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.
gvb
next prev parent reply other threads:[~2008-01-25 0:23 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 [this message]
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=47992BFE.5000906@gmail.com \
--to=gvb.uboot@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox