From owner-freebsd-security Mon Mar 18 13:36: 9 2002 Delivered-To: freebsd-security@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 9355437B400 for ; Mon, 18 Mar 2002 13:35:19 -0800 (PST) Received: from caddis.yogotech.com (caddis.yogotech.com [206.127.123.130]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id OAA27232; Mon, 18 Mar 2002 14:35:17 -0700 (MST) (envelope-from nate@yogotech.com) Received: (from nate@localhost) by caddis.yogotech.com (8.11.6/8.11.6) id g2ILZHh05055; Mon, 18 Mar 2002 14:35:17 -0700 (MST) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15510.23957.153589.130354@caddis.yogotech.com> Date: Mon, 18 Mar 2002 14:35:17 -0700 To: Brett Glass Cc: security@FreeBSD.ORG Subject: Re: FreeBSD Ports Security Advisory FreeBSD-SA-02:18.zlib In-Reply-To: <4.3.2.7.2.20020318140524.00e5bd60@nospam.lariat.org> References: <4.3.2.7.2.20020318140524.00e5bd60@nospam.lariat.org> X-Mailer: VM 6.96 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > >You mean like the 4.5 security branch (RELENG_4_5)? > > I don't use CVS on production machines (nor should one > do so; This I disagree with. > it's not a good idea to rebuild a production machine's > code nightly). This I agree with. Please explan why using CVS == building code nightly? > What I really need is a stream of patches -- RELENG_4_5 is a stream of buildable patches. Nothing gets committed to that tree unless it works (barring unforseen errors that even occur in patches from Real (tm) vendors). > or, failing that, builds that I can install seamlessly > as updates. CVsup RELENG_4_5. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message