Date: Sun, 6 Jan 2002 22:52:11 +0200 From: Peter Pentchev <roam@ringlet.net> To: Mike Barcroft <mike@FreeBSD.org> Cc: Dag-Erling Smorgrav <des@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/lib/libfetch Makefile common.c common.h fetch.3 fetch.c fetch.h file.c ftp.c http.c Message-ID: <20020106225211.I314@straylight.oblivion.bg> In-Reply-To: <20020106163356.E86911@espresso.q9media.com>; from mike@FreeBSD.org on Sun, Jan 06, 2002 at 04:33:56PM -0500 References: <200112180944.fBI9ioK99527@freefall.freebsd.org> <20011225162803.C304@straylight.oblivion.bg> <20020106222223.F314@straylight.oblivion.bg> <20020106163356.E86911@espresso.q9media.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jan 06, 2002 at 04:33:56PM -0500, Mike Barcroft wrote: > Peter Pentchev <roam@ringlet.net> writes: > > This is still an issue: libfetch does not compile on -stable with > > WARNS_WERROR set. I guess it would not compile on -current, either, > > was it not for David O'Brien's changing the WARNS granularity, so > > WARNS=2 is 'mostly harmless' now :) > > I think WARNS set on -STABLE is mostly meaningless, and mainly serves > to help reduce differences between -CURRENT and -STABLE. There are big parts of the source tree that are different in -current and -stable, '..and never the twain shall meet'. There are also nuisances like me, who just like to make sure everything is - or at the very least, seems to be - all right :) But anyway, see my other message: the problem is not with DES's libfetch, it is in the WARNS handling in -stable.. which makes this little side discussion quite relevant, in fact. G'luck, Peter -- I am the thought you are now thinking. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020106225211.I314>