Date: Tue, 2 Jul 2002 11:14:30 +0200 From: "Plamen Petkov" <plamendp@bgstore.com> To: "Kevin Kinsey, DaleCo, S.P." <kdk@daleco.biz> Cc: <freebsd-security@FreeBSD.ORG> Subject: Re: security fixes Message-ID: <007b01c221a8$e9a19ba0$62494fd9@f2f.cx> References: <20020701141839.V50179-100000@mohegan.mohawk.net> <008401c22136$08d62e00$edec910c@fbccarthage.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Since 2-3 years I don't have any problems cvsuping only *-STABLE. It's a matter of trust in core team, all commiters, etc. that -STABLE is *realy* stable :-) So, I always cvsup -STABLE (RELENG_4 at the moment) and everything is OK. Of course, I first cvsup at dev machine and test if it's Ok then cvsup on production machine(s). Just to be sure there is nothing wrong with cvsup server I use. Regards, --- Plamen D. Petkov, ICQ# 2214327 plamendp@bgstore.com http://www.bgstore.com > > With all the traffic surrounding these recent vulnerabilities, it's a > > little confusing to know what one has to do and need not do. Let me ask > > this one question, please: > > > > In cvsup'ing the patched sources, if I have a 4.6-RELEASE box, should I > > cvsup RELENG_4_6 and for the earlier 4.x machines cvsup RELENG_4 ??? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?007b01c221a8$e9a19ba0$62494fd9>