Date: Mon, 01 Apr 2002 00:47:52 -0600 From: Christopher Schulte <schulte+freebsd@nospam.schulte.org> To: Larry Vaden <vaden@texoma.net>, Nathan Reilly <nathan@bbuzzed.cx> Cc: security@FreeBSD.ORG Subject: Re: Why update the world because of OpenSSH? Message-ID: <5.1.0.14.0.20020401004221.0694bcc8@pop3s.schulte.org> In-Reply-To: <5.1.0.14.2.20020401003241.058c7668@mail.texoma.net> References: <3CA7FDF9.1040702@bbuzzed.cx> <4487.213.112.58.135.1017583220.squirrel@phucking.kicks-ass.org> <5.1.0.14.2.20020331223056.05213e90@mail.texoma.net>
next in thread | previous in thread | raw e-mail | index | archive | help
At 12:35 AM 4/1/2002 -0600, Larry Vaden wrote: >Am I correct in assuming that RELENG_4_5 changes from time to time? Yup. Whenever critical (security) changes are committed. >If that is the case, how does one build 4.5-RELEASEp2 without the exposure >of mods since that release? The current state of RELENG_4_5 is 4.5-RELEASE-p2. That basically means there have been 2 changes to RELENG_4_5 since 4.5-RELEASE came to be. As soon as another commit is made, it will be known as 4.5-RELEASE-p3. You simply synchronize to RELENG_4_5 and get the most current -px state. /usr/src/UPDATING documents the changes made, once you cvsup your sources. >thnx/ldv -- Christopher Schulte http://www.schulte.org/ Do not un-munge my @nospam.schulte.org email address. This address is valid. 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?5.1.0.14.0.20020401004221.0694bcc8>