I am pretty good with using CVS to exert source control over a project - in part because I have made most of the obvious and many of the unobvious mistakes but mostly because I have accumulated a handful of really superb reference sites to which I can refer to sort out anything tricky.
cvs import -kk -I ! new-repository Vendor vendor-tag
cvs update -j 1.4 -j 1.3 hello.c cvs commit -m "putting back the previous version" hello.c
And this tidbit from the UUACS mailing list:
Question:I am attempting to set up cvs where only certain people can write and everyone can read (well most of the time, sometimes only the group can read). I was wondering what people are doing for this?
I have it working doing changing the lock file to be placed in /var/lock/cvs (which is world writtable) and then changing the module to be only writtable by the group.
Seems simple enough, but since the lock directory has to be world writable, someone could go remove a lock while it is checked out... so any better ideas?
Maybe setting the sticky bit would work? Then, only the person who placed the lock can remove it. (ie setting the directory to 1777 instead of 0777 with chmod +t).