From: "Adam J. Richter" <adam@yggdrasil.com>
To: linux-kernel@vger.kernel.org
Cc: c-d.hailfinger.kernel.2003@gmx.net, levon@movementarian.org
Subject: Re: 2.5.69-bk19 "make" messages much less informative
Date: Mon, 26 May 2003 19:44:06 -0700 [thread overview]
Message-ID: <200305270244.h4R2i6E21333@freya.yggdrasil.com> (raw)
Carl-Daniel Hailfinger wrote:
>If something stands out clearly, people tend to notice it. Assuming only
>one person gets annoyed enough to submit fixes for the warnings, this is
>a net win.
>V=0 still works, only the default was changed.
I think the productivity that I would lose from such a build
environment would exceed the fixing of one compiler warning within
a couple of days, perhaps even sooner, and I am only one developer.
Many thanks to John Levon for pointing out that V=1 still
works. Here is a proposed patch, which I have already committed
to my tree.
Adam J. Richter __ ______________ 575 Oroville Road
adam@yggdrasil.com \ / Miplitas, California 95035
+1 408 309-6081 | g g d r a s i l United States of America
"Free Software For The Rest Of Us."
--- linux-2.5.69-bk19/Makefile 2003-05-26 12:26:26.000000000 -0700
+++ linux/Makefile 2003-05-26 18:00:31.000000000 -0700
@@ -107,15 +107,13 @@
# If it is set to "silent_", nothing wil be printed at all, since
# the variable $(silent_cmd_cc_o_c) doesn't exist.
-# To put more focus on warnings, less verbose as default
-
ifdef V
ifeq ("$(origin V)", "command line")
KBUILD_VERBOSE = $(V)
endif
endif
ifndef KBUILD_VERBOSE
- KBUILD_VERBOSE = 0
+ KBUILD_VERBOSE = 1
endif
ifdef C
next reply other threads:[~2003-05-27 2:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 2:44 Adam J. Richter [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-26 22:23 Adam J. Richter
2003-05-26 22:49 ` John Levon
2003-05-27 0:05 ` Carl-Daniel Hailfinger
2003-05-27 4:48 ` Sam Ravnborg
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=200305270244.h4R2i6E21333@freya.yggdrasil.com \
--to=adam@yggdrasil.com \
--cc=c-d.hailfinger.kernel.2003@gmx.net \
--cc=levon@movementarian.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®