From owner-freebsd-questions Sat Mar 6 20:10:34 1999 Delivered-To: freebsd-questions@freebsd.org Received: from mail.rdc1.sfba.home.com (ha1.rdc1.sfba.home.com [24.0.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 80A0314BFF for ; Sat, 6 Mar 1999 20:10:29 -0800 (PST) (envelope-from charon@freethought.org) Received: from c40948-a ([24.1.7.99]) by mail.rdc1.sfba.home.com (InterMail v4.00.03 201-229-104) with SMTP id <19990307041011.TBF21746.mail.rdc1.sfba.home.com@c40948-a>; Sat, 6 Mar 1999 20:10:11 -0800 Message-Id: <3.0.5.32.19990306201001.00978850@mail> X-Sender: tuathadedanann@mail X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Sat, 06 Mar 1999 20:10:01 -0800 To: Steve Carter , freebsd-questions@FreeBSD.ORG From: charon@freethought.org Subject: Re: Keeping -RELEASE up to date In-Reply-To: <19990306205520.A5821@globalcenter.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 08:55 PM 3/6/99 -0700, Steve Carter wrote: >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? -STABLE _is_ the tracking for -RELEASE, basically, since each release is taken from the -STABLE branch. As said in the Handbook (18.2. Staying Stable with FreeBSD), "the stable branch is effectively a bug-fix stream relative to the previous release." -charon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message