From owner-freebsd-questions  Sat Mar  6 19:55:41 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 4B69F152EB
	for <freebsd-questions@FreeBSD.ORG>; Sat,  6 Mar 1999 19:55:40 -0800 (PST)
	(envelope-from scarter@magi.primenet.com)
Received: (from scarter@localhost)
	by magi.primenet.com (8.9.3/8.9.1) id UAA05833
	for freebsd-questions@FreeBSD.ORG; Sat, 6 Mar 1999 20:55:20 -0700 (MST)
Date: Sat, 6 Mar 1999 20:55:20 -0700
From: Steve Carter <scarter@globalcenter.net>
To: freebsd-questions@FreeBSD.ORG
Subject: Keeping -RELEASE up to date
Message-ID: <19990306205520.A5821@globalcenter.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95i
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I am pretty seasoned with Unix, but pretty recent to FreeBSD.

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


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message