From owner-freebsd-questions@FreeBSD.ORG Thu May 17 15:12:50 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 09F4416A401 for ; Thu, 17 May 2007 15:12:50 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from ns1.jnielsen.net (ns1.jnielsen.net [69.55.238.237]) by mx1.freebsd.org (Postfix) with ESMTP id E223A13C448 for ; Thu, 17 May 2007 15:12:49 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from localhost (jn@ns1 [69.55.238.237]) (authenticated bits=0) by ns1.jnielsen.net (8.12.9p2/8.12.9) with ESMTP id l4HFCkc5040617; Thu, 17 May 2007 11:12:49 -0400 (EDT) (envelope-from lists@jnielsen.net) From: John Nielsen To: freebsd-questions@freebsd.org Date: Thu, 17 May 2007 11:12:30 -0400 User-Agent: KMail/1.9.6 References: <340a29540705170804r51e4d073w9da7eaf9203e85bd@mail.gmail.com> In-Reply-To: <340a29540705170804r51e4d073w9da7eaf9203e85bd@mail.gmail.com> X-Face: #X5#Y*q>F:]zT!DegL3z5Xo'^MN[$8k\[4^3rN~wm=s=Uw(sW}R?3b^*f1Wu*.<=?utf-8?q?of=5F4NrS=0A=09P*M/9CpxDo!D6?=)IY1w<9B1jB; tBQf[RU-R<,I)e"$q7N7 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200705171112.30887.lists@jnielsen.net> X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on ns1.jnielsen.net X-Virus-Status: Clean Cc: Andrew Falanga Subject: Re: A little bit of help understanding CVS and cvsup X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 May 2007 15:12:50 -0000 On Thursday 17 May 2007 11:04:06 am Andrew Falanga wrote: > Hi, > > This question probably hasn't much to do with CVS directly but using > cvsup. I want/need to update a 6.0-RELEASE system. However, this > system has some critical data on it and I'd rather not move to code > that is perhaps experimental or "bleeding-edge" technology. I see in > /usr/share/examples/cvsup several supfiles named various things. I > see from the handbook that standard-supfile applies to, what seems > like, the bleeding-edge and the stable-supfile is what I'm looking for > .. yes? > > How do I ensure I update the sources to the most current, STABLE, branch? The main difference between the examples files is the cvs tag used. The "." tag will get you 7.0-CURRENT. Very much bleeding edge, almost certainly not what you want. The "RELENG_6" tag will get you 6-STABLE. This is the branch that will eventually become 6.3-RELEASE. Everything in this branch is reasonably conservative and well-tested, but there is still some new code and features. This might be what you want. The "RELENG_6_2" tag will get you 6.2-RELEASE-pX, where X is the current patch revision level. This is 6.2-RELEASE with security and critical patches only, no new features. This is probably what you want, unless there's a feature in -STABLE that you can't live without. JN