From owner-freebsd-stable Sun Jan 13 13:40: 0 2002 Delivered-To: freebsd-stable@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-107-33.dsl.lsan03.pacbell.net [64.169.107.33]) by hub.freebsd.org (Postfix) with ESMTP id 2CFBE37B405 for ; Sun, 13 Jan 2002 13:39:49 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id BFC7266E18; Sun, 13 Jan 2002 13:39:42 -0800 (PST) Date: Sun, 13 Jan 2002 13:39:42 -0800 From: Kris Kennaway To: Mark.Andrews@isc.org Cc: Kris Kennaway , Mark_Andrews@isc.org, alexus , freebsd-stable@freebsd.org Subject: Re: Fw: Cron /usr/local/bin/cvsup -g -h cvsup.FreeBSD.org /usr/share/examples/cvsup/stable-supfile >/dev/null;cd /usr/src;make buildworld >/dev/null;make buildkernel >/dev/null Message-ID: <20020113133942.A17818@xor.obsecurity.org> References: <20020112220311.A923@xor.obsecurity.org> <200201131423.g0DENGs00755@drugs.dv.isc.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="SLDf9lqlvOQaIe6s" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200201131423.g0DENGs00755@drugs.dv.isc.org>; from Mark.Andrews@isc.org on Mon, Jan 14, 2002 at 01:23:16AM +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --SLDf9lqlvOQaIe6s Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 14, 2002 at 01:23:16AM +1100, Mark.Andrews@isc.org wrote: > > I think you're missing my point. Yes, they're probably pieces of code > > which should be fixed by the developers, but they're not abnormal > > messages from the FreeBSD build process (since they're there all the > > time) which the end user needs to take action over. > >=20 > > Kris > >=20 >=20 > Except not all of them are there all the time. There are > changes to the code base and these changes can generate new > warnings that happen to be over looked because of all the > other warnings that are being ignored. >=20 > The problem is to be able to tell which warning falls into > which category. It it the same old warning or is it a new > one that really should be addressed. Again, you seem to be missing my point. The *end user* needs to do nothing about these. Coders and developers shouldn't be introducing new warnings into FreeBSD, and they should eventually fix the ones which are already there, but end users are not coders or developers. This discussion seems to be going in circles, so I'll end it here. Kris --SLDf9lqlvOQaIe6s 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 iD8DBQE8Qf6dWry0BWjoQKURAksCAJ9Ud12sCYefh4CT6esygJ3IvyxNbgCgo8nL 1meq3UAFozIT5plwHabiONs= =MwdD -----END PGP SIGNATURE----- --SLDf9lqlvOQaIe6s-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message