From owner-freebsd-questions Sat Oct 17 18:54:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA17393 for freebsd-questions-outgoing; Sat, 17 Oct 1998 18:54:35 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.240.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA17387 for ; Sat, 17 Oct 1998 18:54:33 -0700 (PDT) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.8.8/8.8.8) id SAA25531; Sat, 17 Oct 1998 18:53:59 -0700 (PDT) (envelope-from mph) Message-ID: <19981017185358.A25478@wopr.caltech.edu> Date: Sat, 17 Oct 1998 18:53:58 -0700 From: Matthew Hunt To: Karl Hanmore , freebsd-questions@FreeBSD.ORG Subject: Re: 3.0-Release References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Karl Hanmore on Sun, Oct 18, 1998 at 11:24:40AM +1000 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 18, 1998 at 11:24:40AM +1000, Karl Hanmore wrote: > I am trying to cvsup from 2.2.7-STABLE to 3.0-RELEASE, anyone have > a supfile they can mail me, as this is driving me insane.... > > I tried changing the release tag to RELENG_3_0 but that didn't work :( > Any pointers?? There is no RELENG_3_0 tag (analogous to RELENG_2_2) because 3.0 is not on a branch, like 2.2 is. If you want 3.0.0-RELEASE, get RELENG_3_0_0_RELEASE. This is analogous to getting, say, RELENG_2_2_7_RELEASE to get 2.2.7-R. If you want the latest 3.0 code, use a dot as the tag ("tag=."), indicating that you want the "head" of the tree. This is analogous to using RELENG_2_2 to track 2.2-STABLE. If you use cvsup to track the ports collection, you can look at it and note that you're also using "tag=." there, because it's unbranched. -- Matthew Hunt * Science rules. http://www.pobox.com/~mph/pgp.key for PGP public key 0x67203349. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message