Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 5 Feb 2002 20:08:12 -0800
From:      Kris Kennaway <kris@obsecurity.org>
To:        "Jeroen C.van Gelderen" <jeroen@vangelderen.org>
Cc:        Kris Kennaway <kris@obsecurity.org>, David O'Brien <obrien@FreeBSD.ORG>, Ruslan Ermilov <ru@FreeBSD.ORG>, Mark Murray <markm@FreeBSD.ORG>, current@FreeBSD.ORG, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG
Subject:   Re: Not committing WARNS settings...
Message-ID:  <20020205200812.A50411@xor.obsecurity.org>
In-Reply-To: <526E436C-1AAF-11D6-B59E-00306580B1CA@vangelderen.org>; from jeroen@vangelderen.org on Tue, Feb 05, 2002 at 10:12:15PM -0500
References:  <20020205100414.A44541@xor.obsecurity.org> <526E436C-1AAF-11D6-B59E-00306580B1CA@vangelderen.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--J/dobhs11T7y2rNN
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Feb 05, 2002 at 10:12:15PM -0500, Jeroen C.van Gelderen wrote:

> > On Tue, Feb 05, 2002 at 07:20:46AM -0800, David O'Brien wrote:
> >> On Mon, Feb 04, 2002 at 07:06:54PM -0800, Kris Kennaway wrote:
> >>> If you use the argument that one shouldn't set WARNS because a new
> >>> compiler will cause the tree to break, then there's no point having it
> >>> at all since that condition will always be true.
> >>
> >> The difference is _impending_.
> >
> > EPARSE.
>=20
> David is about to switch to GCC 3.0 and I guess he does not like moving=
=20
> targets. I would expect that for the GCC 4.0 upgrade a similar freeze=20
> request will go out. And that seems fair enough since it does not=20
> prevent anyone from applying the actual code fixes. We want to make this=
=20
> import stuff as easy on David as we can, no? It is a job from hell=20
> already.

All David has to do is set WARNS=3D0 or NO_WERROR=3D1 in <bsd.sys.mk> or
/etc/defaults/make.conf temporarily when he tests and commits the
changeover, and he'll sidestep all the problems.  There's no need to
impose restrictions on the activities of other committers.

It's really not a big deal, IMO.

Kris

--J/dobhs11T7y2rNN
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)
Comment: For info see http://www.gnupg.org

iD8DBQE8YKwsWry0BWjoQKURAjJ2AJ9yWzPfb0EBzKwh/o1bmDoCA5WReQCePqO/
XqXoZEU+6izng3aCOEh/BvE=
=bhTd
-----END PGP SIGNATURE-----

--J/dobhs11T7y2rNN--

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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020205200812.A50411>