From owner-freebsd-hackers Sun Dec 8 13:23: 1 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5EA3037B401 for ; Sun, 8 Dec 2002 13:23:00 -0800 (PST) Received: from warez.scriptkiddie.org (uswest-dsl-142-38.cortland.com [209.162.142.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18DCE43E4A for ; Sun, 8 Dec 2002 13:22:56 -0800 (PST) (envelope-from lamont@scriptkiddie.org) Received: from [192.168.69.11] (unknown [192.168.69.11]) by warez.scriptkiddie.org (Postfix) with ESMTP id C3BF362D1A for ; Sun, 8 Dec 2002 13:22:49 -0800 (PST) Date: Sun, 8 Dec 2002 13:22:49 -0800 (PST) From: Lamont Granquist To: freebsd-hackers@freebsd.org Subject: CVS_LOCAL_BRANCH_NUM? Message-ID: <20021208112628.H11375-100000@coredump.scriptkiddie.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've been struggling all weekend to setup a local CVS repo mirror, and I guess I've done that successfully, but I can't figure out what is going on with CVS_LOCAL_BRANCH_NUM. My understanding is that if I set it to a large number "63000" that it should tag branches that I make with values roughly that large. You can see from below that what I'm getting though is low-numbered branches. I'm confused. This is what I did on both -current and 4.6-release: setenv CVS_LOCAL_BRANCH_NUM 63000 cvs rtag -b -r RELENG_4_7 RELENG_4_LCG src And this is what I get -- shouldn't that be something like 1.229.63000? cvs status UPDATING =================================================================== File: UPDATING Status: Up-to-date Working revision: 1.229 Repository revision: 1.229 /cvs/src/UPDATING,v Sticky Tag: RELENG_4_LCG (branch: 1.229.4) Sticky Date: (none) Sticky Options: (none) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message