I can think of specific examples where testing, etc. may not happen in a
'working copy' of the code. For example, one of the projects I am using
cvs for is a website. I have a script in cvs that, upon checkin, copies
the file over to a directory so that the 'current' cvs version of the
site can
On Wed, 2002-10-09 at 13:58, Greg A. Woods wrote:
[ On , October 9, 2002 at 10:03:08 (-0400), Adam Bregenzer wrote: ]
Subject: Re: Tag locking change
I can think of specific examples where testing, etc. may not happen in a
'working copy' of the code. For example, one of the projects I
On Wed, 2002-10-09 at 14:58, Greg A. Woods wrote:
[ On , October 9, 2002 at 14:26:15 (-0400), Adam Bregenzer wrote: ]
Subject: Re: Tag locking change
On Wed, 2002-10-09 at 13:58, Greg A. Woods wrote:
Yes, sure, but that copying is done (or at least the source for the
copying
Try passing the branch tag of the branch you want to branch off of to -r
instead of its number.
Like:
cvs rtag -b -r OLD_BRANCH_TAG NEW_BRANCH_TAG fred.cc
Disclaimer: I can't say I've tried that before, but I don't see any
reason why it wouldn't work. Can anybody on the list verify that?
Adam
Validation :P
Adam
-Forwarded Message-
From: James Stalker [EMAIL PROTECTED]
To: Adam Bregenzer [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: Issue creating branch tag off of numeric revision
Date: 19 Sep 2002 15:48:19 +0100
On Thu, Sep 19, 2002 at 09
Tag the current ERASER branch, checkout a fresh copy off the HEAD
branch, merge your changes from the new ERASER tag into your working
copy. If you have any conflicts from development done on the HEAD
branch after the ERASER branch started either resolve them, or to
discard them merge from the
AFIAK the issue is not with where the working copy is stored, as long as
you are the only one accessing the working copy. The issue is where the
repository is stored/accessed from. Replacing the CVS protocol that's
using pserver in your diagram with a local protocol accessing the
repository via
First of all, where do you want your repository located? the 'init'
command will create the CVSROOT folder for you. *If* you have not been
able to import anythign into cvs I recommend doing this:
rm -rf /home/cvs# WARNING this will erase any existing modules
mkdir /home/cvs
cvs -d
