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>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.94.961125200854.25765A-100000>