From owner-freebsd-hackers@FreeBSD.ORG Mon Oct 12 08:43:51 2009 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C77221065672 for ; Mon, 12 Oct 2009 08:43:51 +0000 (UTC) (envelope-from uqs@spoerlein.net) Received: from acme.spoerlein.net (cl-43.dus-01.de.sixxs.net [IPv6:2a01:198:200:2a::2]) by mx1.freebsd.org (Postfix) with ESMTP id 5BF898FC26 for ; Mon, 12 Oct 2009 08:43:51 +0000 (UTC) Received: from acme.spoerlein.net (localhost.spoerlein.net [IPv6:::1]) by acme.spoerlein.net (8.14.3/8.14.3) with ESMTP id n9C8heWD098282 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Oct 2009 10:43:40 +0200 (CEST) (envelope-from uqs@spoerlein.net) Received: (from uqs@localhost) by acme.spoerlein.net (8.14.3/8.14.3/Submit) id n9C8hds5098281; Mon, 12 Oct 2009 10:43:39 +0200 (CEST) (envelope-from uqs@spoerlein.net) Date: Mon, 12 Oct 2009 10:43:38 +0200 From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= To: Ed Schouten Message-ID: <20091012084337.GI36937@acme.spoerlein.net> Mail-Followup-To: Ed Schouten , FreeBSD Hackers References: <20091011145021.GG36937@acme.spoerlein.net> <20091011170918.GU71731@hoeg.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20091011170918.GU71731@hoeg.nl> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: FreeBSD Hackers Subject: Re: RFC: Big Makefile patch for WARNS settings X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Oct 2009 08:43:51 -0000 On Sun, 11.10.2009 at 19:09:18 +0200, Ed Schouten wrote: > Hi Ulrich, > > * Ulrich Spörlein wrote: > > Comments? Committers? > > Wouldn't it better to address the root of the problem while there? ;-) It sure would, but someone[TM] would have to fix all problems for a top-level dir in a short time frame before new code hits the repo. Or, we might end up with individual WARNS on 98% of the subdirs and need a big sweeping patch to then flip the default anyway, so why not now? It raises the bar for new code entering the tree and we need individual WARNS lowering anyway due to contrib code. The only question then is, when do we want to churn. Right now when a patch is available or do we wait and hope that someday all will be better? Anyway, interest seems low for such a big patch so I guess I'll have to divvy it up for better digestion. Regards, Uli