From: John Spencer <maillist-musl@barfooze.de>
To: musl@lists.openwall.com
Cc: Luca Barbato <lu_zero@gentoo.org>
Subject: Re: [PATCH] makefile: add silent rules
Date: Thu, 07 Jun 2012 15:19:33 +0200 [thread overview]
Message-ID: <4FD0AA65.20107@barfooze.de> (raw)
In-Reply-To: <1339056785-21979-1-git-send-email-lu_zero@gentoo.org>
On 06/07/2012 10:13 AM, Luca Barbato wrote:
> make V=1 to disable them
> ---
>
please see the mail georgi sent to the list at 13th may and the followup
responses.
maybe 10% of users want a "quiet" build, so why force your preference on
anybody ?
if it was the other way around (explicitly enable the "quiet" stuff), i
wouldn't be as opposed to this idea.
but effectively it gains you nothing except "awesome looks" *sigh*, and
adds additional bloat to the Makefile.
-- JS
prev parent reply other threads:[~2012-06-07 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 8:13 Luca Barbato
2012-06-07 13:12 ` Igmar Palsenberg
2012-06-07 13:18 ` Rich Felker
2012-06-07 13:19 ` John Spencer [this message]
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=4FD0AA65.20107@barfooze.de \
--to=maillist-musl@barfooze.de \
--cc=lu_zero@gentoo.org \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).