From owner-freebsd-hackers  Mon Nov 25 20:18:19 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id UAA06598
          for hackers-outgoing; Mon, 25 Nov 1996 20:18:19 -0800 (PST)
Received: from misery.sdf.com (misery.sdf.com [204.244.210.193])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA06560;
          Mon, 25 Nov 1996 20:17:53 -0800 (PST)
Received: from misery.sdf.com ([204.244.213.33]) by misery.sdf.com with SMTP id <1344-9462>; Mon, 25 Nov 1996 20:17:40 -0800
Date: 	Mon, 25 Nov 1996 20:17:34 -0800 (PST)
From: Tom Samplonius <tom@sdf.com>
To: hackers@freebsd.org
cc: peter@freebsd.org
Subject: Local CVS commits (and cvsup)
Message-ID: <Pine.NEB.3.94.961125200854.25765A-100000@misery.sdf.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


  I have some questions about the CVS "Local Commit" feature.  I
understand the basic idea of setting CVS_LOCAL_BRANCH_NUM, but not the
actual procedure.

  I assume something like the following is required:

cvs co src
(edit a file)
setenv CVS_LOCAL_BRANCH_NUM 1000
cvs commit (edited file)	# commit is made on unique, new branch


  But what is recommended way of hacking stuff in $CVSROOT/CVSROOT to
allow non-freefall committers?  How would I "protect" local changes in
this directory from removal by cvsup?  Since this directory is just book
keeping, and technically not part of the repository, cvsup's local commit
protection will not work on them will it, right? 

Tom