[This is a repost of an earlier message which didn't show up in the list archives - sorry if it's a duplicate] Hi, I thought people might like to know that the CVS reference manual is now available a
Hi there, i dont have time for ever - i only need a good instructio or book, to install and configure cvsnt on WindowXP. This is what i expect: - Installation - Create Repository - Install Users i fo
Hi, i have read the Book of Karl Fogel "Open Source Development with CVS" in deepth and figured out a bug. (IMHO) I have tested it with CVS 1.11. The Chapter "The modules File" There has been an exam
All About CVS table of contents: http://march-hare.com/pdf/ebooktoc2502.pdf March Hare Software have released CVS Suite. CVS Suite includes * the eBook "All About CVS: How to Design and Build an Effe
Hmm, interesting read, but doesn't specifically address the issue of parallel developents in different branches. For example, HEAD, Beta, RC, Stable, and Fix where each of these branches is being wor
Alicia, I had a hand in writing the eBook "All About CVS" so I'd recommend that one ;) Essential CVS which you already have though has been the one book that most CVS Admins have read for many years
unsubscribe me... I don't want your emails. Send Info-cvs mailing list submissions to address@hidden To subscribe or unsubscribe via the World Wide Web, visit http://mail.gnu.org/mailman/listinfo/inf
When I originally replied to this email, I believe we agreed it wouldn't quite work for a parallel development scheme. I've since done some more reading and digesting of information, and think it mig
There was a similar thread about Build Processes (Release Engineering) in CVS back in August, started by Bil Joga. My reply outlines our tagging and branching model: http://mail.gnu.org/pipermail/inf
Mark, I think you are using cvs in local mode. If you where using it in a client/server mode, cvs would have the tmp files a location on the server (the /tmp by default with pserver). Since you are i
Output from a trigger script: use Cwd; use strict; use Carp; my $pwd = cwd(); open (F, ">/tmp/junk/test.txt") or croak ('can not open /tmp/junk/test.txt'); print F "PWD: $pwd\n"; print F map { "$_\n"
I just did some testing, and modifying the server tmp copies is a real bad idea, like Dennis said. But it is good that CVS makes the to-be-commited files available (whether or not by design) to the t
Mark, Is this really a good idea? If you do what you are proposing, after you commit a file, changes will be made to the file (unbeknownst to you) and I suspect your local copy will immediately be ou
Hi Mark, Thanks for the response. I know how to get the variables though, what I am trying to do is actually open up the files that are being committed. So for example, suppose you wanted to run a co
Andrew, The short answer is that for every "release" it is typical to create a branch, and for each version of a release sent out you normally create a tag. Both are managed using the "cvs tag" comma
FWIW, when I do 'cvs rlog -R .' it asserts: cvs: recurse.c:642: do_recursion: Assertion `strstr (repository, "/./") == ((void *)0)' failed. cvs [rlog aborted]: received abort signal I'm using 1.11.19
Corey, Have a look at this http://ximbiot.com/cvs/manual/cvs-1.11.21/cvs_5.html#SEC54. It gives good overview of branching and merging. I personally find it less painful if development is done on the
Corey, Well that's only one way to use CC of course, I've used it a little and I know you don't have to do things that way (because I didn't) - I didn't get into the rational unified process enough t