From owner-freebsd-questions Sat Mar 6 21:42: 9 1999 Delivered-To: freebsd-questions@freebsd.org Received: from magi.primenet.com (magi.primenet.com [206.165.0.136]) by hub.freebsd.org (Postfix) with ESMTP id 3985F14C33 for ; Sat, 6 Mar 1999 21:42:08 -0800 (PST) (envelope-from scarter@magi.primenet.com) Received: (from scarter@localhost) by magi.primenet.com (8.9.3/8.9.1) id WAA05944; Sat, 6 Mar 1999 22:41:32 -0700 (MST) Date: Sat, 6 Mar 1999 22:41:32 -0700 From: Steve Carter To: W Gerald Hicks Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Keeping -RELEASE up to date Message-ID: <19990306224132.A5933@globalcenter.net> References: <19990306205520.A5821@globalcenter.net> <199903070416.XAA05477@bellsouth.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199903070416.XAA05477@bellsouth.net>; from W Gerald Hicks on Sat, Mar 06, 1999 at 11:16:52PM -0500 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG W Gerald Hicks wrote: > > I am pretty seasoned with Unix, but pretty recent to FreeBSD. > > Welcome! > > > I have read about using cvsup to keep -CURRENT and -STABLE trains up to > > date, but how does one keep the -RELEASE up to date? Is there a tag for > > -RELEASE also, a la: > > > > *default release=cvs tag=RELENG_3 > > > > I am running 3.0-RELEASE and would like to use cvsup, or some other > > mechanism for keep my system up to date in terms of bug fixes and the > > like. Am I missing something fundamental? > > > > -Steve > > The tag as you've specified it (RELENG_3) is the correct one for > keeping a 3.x release -STABLE. > > The tag 'RELENG_3_0_0_RELEASE' was simply a snapshot at that point > in time on branch RELENG_3. Thanks, that cleared a bunch of fog for me. > I'd recommend getting warmed up to mergemaster if you plan to take > your system from 3.0-RELEASE to 3.1-STABLE. I'd recommend doing so. I don't know what this does but I'll read up on it.....:) Thanks again, -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message