From owner-freebsd-current  Wed Feb 27 15:20:27 2002
Delivered-To: freebsd-current@freebsd.org
Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39])
	by hub.freebsd.org (Postfix) with ESMTP id EBE9A37B41F
	for <current@FreeBSD.ORG>; Wed, 27 Feb 2002 15:20:17 -0800 (PST)
Received: from InterJet.elischer.org ([12.232.206.8])
          by rwcrmhc53.attbi.com
          (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP
          id <20020227232016.XZED2951.rwcrmhc53.attbi.com@InterJet.elischer.org>;
          Wed, 27 Feb 2002 23:20:16 +0000
Received: from localhost (localhost.elischer.org [127.0.0.1])
	by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id PAA02498;
	Wed, 27 Feb 2002 15:18:27 -0800 (PST)
Date: Wed, 27 Feb 2002 15:18:26 -0800 (PST)
From: Julian Elischer <julian@elischer.org>
To: Peter Wemm <peter@wemm.org>
Cc: Alfred Perlstein <bright@mu.org>,
	Matthew Dillon <dillon@apollo.backplane.com>,
	FreeBSD current users <current@FreeBSD.ORG>
Subject: Re: controversial fix or some errors breaking LINT 
In-Reply-To: <20020227231509.EB2B93809@overcee.wemm.org>
Message-ID: <Pine.BSF.4.21.0202271518000.97278-100000@InterJet.elischer.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG


I presume then that you also feel that allowing bcopy to copy 
volatile regions is a bad idea?


On Wed, 27 Feb 2002, Peter Wemm wrote:

> Alfred Perlstein wrote:
> > * Matthew Dillon <dillon@apollo.backplane.com> [020227 14:51] wrote:
> > > 
> > > :
> > > :ok so I leave it to other people to fix LINT
> > > :I'm not going near it any more
> > > 
> > >     It's the responsibility of whoever added -Werror to the default
> > >     compile to unbreak the tree, either by fixing the problem or by
> > >     backing out his commit.
> > 
> > No.  Leave it in, this will benifit us all in the long run.
> > 
> > In fact it was the _only_ way I was able to get people clean
> > up bad code at a former job and I strongly support keeping
> > -Weerror enabled.
> 
> If there are files that are too hard to fix, or vendor files, or the fix
> isn't clear, we should use the nowerror conf/files* flags.
> 
> It is important that we stop new warnings turning up when the compile
> output is so damn large that it hides things.
> 
> I will do a pass over things now and see what I can do.
> 
> Cheers,
> -Peter
> --
> Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au
> "All of this is for nothing if we don't go to the stars" - JMS/B5
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message