From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [RFC] make output of compiling a bit less verbose to make warnings more visible
Date: Tue, 02 Sep 2008 22:43:54 +0300 [thread overview]
Message-ID: <48BD977A.5090305@nic.fi> (raw)
In-Reply-To: <20080902192740.GD9070@thorin>
Robert Millan wrote:
> On Tue, Sep 02, 2008 at 07:10:05PM +0200, Felix Zielcke wrote:
>> Am Dienstag, den 02.09.2008, 18:43 +0200 schrieb Felix Zielcke:
>>> Hello,
>>>
>>> I think it would be good if the output from compiling wouldn't be that
>>> verbose.
>> Urm thanks again to Vesa who remembered that Colin brought that topic
>> originally up here.
>>
>> http://lists.gnu.org/archive/html/grub-devel/2008-06/msg00248.html
>>
>> I really would love to have this somehow commited :)
>
> I don't remember that discussion well; ISTR I complained. Maybe that
> stopped it? Anyway, as long as it's user-selectable it's not a problem
> for me. Maybe I even end up using it ;-)
I think the strength was that you could provide V=99 (or something like
that to give previous behavior ("debug feature").
So basically that is completed.
Only thing perhaps would need attention is to show that now we compile
for HOST CC and now for TARGET CC or so.
next prev parent reply other threads:[~2008-09-02 20:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 16:43 [RFC] make output of compiling a bit less verbose to make warnings more visible Felix Zielcke
2008-09-02 17:10 ` Felix Zielcke
2008-09-02 19:27 ` Robert Millan
2008-09-02 19:43 ` Vesa Jääskeläinen [this message]
2008-09-02 20:47 ` Colin D Bennett
2008-09-03 6:59 ` Felix Zielcke
2008-09-03 8:37 ` Bean
2008-09-03 10:37 ` Felix Zielcke
2008-09-02 17:30 ` Javier Martín
2008-09-03 7:05 ` Hans Lambermont
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=48BD977A.5090305@nic.fi \
--to=chaac@nic.fi \
--cc=grub-devel@gnu.org \
/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.