From owner-cvs-sys  Thu Oct  3 01:39:54 1996
Return-Path: owner-cvs-sys
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id BAA14670
          for cvs-sys-outgoing; Thu, 3 Oct 1996 01:39:54 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA14632;
          Thu, 3 Oct 1996 01:39:40 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id SAA07566; Thu, 3 Oct 1996 18:36:50 +1000
Date: Thu, 3 Oct 1996 18:36:50 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199610030836.SAA07566@godzilla.zeta.org.au>
To: jkh@time.cdrom.com, peter@spinner.dialix.com
Subject: Re: cvs commit: src/sys/i386/isa syscons.c
Cc: cvs-all@freefall.freebsd.org, CVS-committers@freefall.freebsd.org,
        cvs-sys@freefall.freebsd.org, jkh@freefall.freebsd.org,
        msmith@atrad.adelaide.edu.au, sos@FreeBSD.org
Sender: owner-cvs-sys@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>BTW, since these warnings are only really useful for the developers, I'd
>suggest we turn *off* the *extra* warnings for the kernel by default on
>release branches just before rolling it.  It doesn't help to scare the
>natives by having thousands of warnings that only have meaning for
>developers.

An easy task, since -Wunused has never been in a release.  Very few
warnings are enabled in 2.1.5R; I guess there would be about 20000
lines of warnings instead of only 7000 if it were compiled with the
-current gcc and warning flags.

Bruce