Ray, Try and get a good book on the subject, eg: "Essential CVS", or the march-hare eBook "All About CVS", or at least do a google search for "cvs tutorial linux" and read one or three of those begor
For cvs 1.11.x and 1.12.x, the CVS directory in the repository holds the CVS/fileattr files. This is where book-keeping concerning who has done 'cvs watch' and 'cvs edit' on various files. This is a
The CVS/fileattr files are there to do book keeping on advisory locking and 'cvs watch' files. You should be able to remove any of those files without hurting the correct operation of the repository.
The name of the file mentioned below should be cvsuseradmins, and not cvsadminusers. My bad :-( --Original Message-- From: address@hidden [mailto:address@hidden On Behalf Of Rudy Zung Sent: Wednesday
Two scripts supplied gratis and as is. Written specifically for my needs, and I am unlikely to entertain any maintenance requests for it. Idiosyncracies: call cvsuser script with arguments (see below
Keep development on the trunk and always branch/tag the whole repo. Shameless plug for our own book: http://march-hare.com/cvsnt/features/book/ One variation is to use a "magic branch" (CVSNT only -
Correct. CVS works best if most development occurs on the trunk. Correct. You should also tag the branch (e.g. release1_merged) to mark the changes that have already been merged to the trunk. Otherwi
RCS tags are not expensive. Even lots of tags are not a big problem. CVS is mostly using RCS format under the covers. A new CVS branch when created does not actually introduce any new delta records u
A friend of mine has been using CVS for some time and also wants to start making more use of branches, but he has had some opposition from some of his team members. One of the main reasons they have
I have been using CVS for some time now and regularly make use of branches to carry out new lines of development without affecting the core code base and as far as I am concerned it works very well.
If you aren't going to read the manual, don't bother trying to use CVS. Whatever it is you want to do with version control will absolutely require reading the manual. Seriously, if you aren't willing
That's a rather broad question. There are a lot of ways the users can "mess up the repository". You could probably fill several chapters in a book with the common mistakes users make. Most of these m
If it's a WinCVS question you may want to ask on the cvsgui newsgroup (look on the website where you downloaded WinCVS). If you are importing .xls and .doc files you may prefer to use CVSNT (free GPL
Branches are best for short-term or otherwise limited use. Typically, main development occurs on the trunk with releases tagged. Branches are typically used for bug fixes (some people create a bug fi
Corey, This is not the correct list for WinCVS. The CvsGUI list is here: http://groups.yahoo.com/subscribe/cvsgui Your question is a mixture of process and cvs fundamentals - so there is not necessar
There are several organisations that supply professional CVS services, including ours. See here for our details: http://march-hare.com/cvspro We have two courses: * CVS Design and Administration * Us
Lots of questions! Let me see if I can hack off some of the easy ones, and let the more difficult ones dangle for the experts ::grin:: You can easily create a branch for an earlier point in developme
cvs will work pretty much the same on any Linux, Solaris or Mac OS. Windows is a very different breed though. I can not recommend which OS you should get, but get Jen Vesperman's book: "Essential cvs