Hi Jill, It occurs to me, though, that maybe I could set up a "personal" CVS repository off my home directory (although I'll readily admit that I've never set up a CVS repository of *any* kind before
Start with either the CVS online manual (free) or the "Essential CVS" book by Jennifer Vesperman ($40), or the like. -chris --Original Message-- From: address@hidden [mailto:address@hidden On Behalf
You might consider dropping him a line to let him know of the error/inaccuracy. If there's no email address published, you can always send a snail mail care of the publisher. -- Jim Hyslop Senior Sof
Thank you, I'll look at that. [...] OK, thanks. I'd agree with that, too. I'm still a bit confused about -j, (which is off topic for this thread), I think for the same cognitive reasons that people p
You have some reading to do. http://www.cvshome.org/docs/ These links will lead you to the on-line manual "Version Management with CVS" by Per Cederqvist you will want to become familiar with it. You
Hi Carter, By the time that loginfo is called, the commit has already happened for at least one directory, so failing the remainder of the directories will likely leave the repository in an inconsist
Hi, I have written a perl script to parse some log information from CVS. However, from Karl Fogel's book, Open Source Development with CVS, he states that any nonzero exit from a script/program run b
And some places do it successfully while mixing active development and baseline integrations solely on the trunk. Search the info-cvs archives for "submit/assemble" for details. basis for such a sta
The biggest penalty is managing the complexity - each branch you add means one more branch to which you may have to merge your changes. Failing to merge changes into a branch could result in lost tim
[...] OK, I'll do that, I couldn't think of a narrow enough pattern not to get spadefuls of info from google, etc! I'll probably have to play with that a bit to get a feel for what is happening. I th
--Original Message-- From: Hugh Sasse Staff Elec Eng [mailto:address@hidden Sent: Thursday, April 01, 2004 7:45 AM To: Paul Sander Cc: address@hidden; address@hidden; Fouts Christopher (6452); MKlink
Yes, some places seem to do this with different branches... The book "Open Source Development with CVS" says that you should keep few branches active at any one time. I'm wondering if there are penal
Hello, it seems to me that this would be a pretty common task: Upon commit, I want to export the files in the repository to a location. I looked through the cederquist, and the "CVS Essentials" book,
You might try using -j1:date_spec If it works, '1' would mean 'the trunk'. I have no idea if it will actually work. Doesn't appear that way. But, you can apply a tag using a date spec - so you could:
Hmm. My situation was a bit peculiar: I wanted to merge in *only* the changes that were done in the last 2 days, ignoring changes done before that (which is why I specified the date modifier to HEAD)
HEAD has a specific meaning - it means "the latest revision on the trunk [footnote]". Because you have specified an exact revision, the date component will be ignored (the date component can only be
Hello there, I'm trying to merge a set of changes from HEAD to a branch opened a while back. The changes I would like to merge were committed to HEAD between 2 days ago and today; I'll use ChangeLog
Some people seem to be awfully trusting. Why put that parenthetical observation only after your second alternative? I haven't seen any software company act as if it took responsibility for such dama
[ On Wednesday, February 18, 2004 at 10:21:41 (-0500), Jim.Hyslop wrote: ] You're drastically confusing the concepts involved here. If you can't, or won't, build the software you use yourself then yo
Assuming you have tags to work with: cvs -q diff --brief -r TAG1 -r TAG2 dir1 dir2 | grep RCS | cut -f 3- -d ' ' You can do the same thing with dates: cvs -q diff --brief -D yesterday -D today build