[CLUE-Admin] Anonymous CVS Access
CLUE President
president at clue.denver.co.us
Fri Jan 23 04:15:05 MST 2004
On Thursday 22 January 2004 9:23 pm, Jed S. Baer wrote:
> I think I've flogged the Cederqvist enough on this, so here's the scoop.
...
Jed,
I've been using rcs commands, co and ci, whilst in the CVSROOT directory to
make changes to those files.
I've never tried the 'canonical' way, i.e., check out the CVSROOT project to
modify these files. I was a heavy rcs user before cvs and so it was natural
for me to cd to CVSROOT and do ci, co. Until you said something, it didn't
occur to me that CVSROOT is simply another cvs project.
But since I'm curious, I looked at the cvs manual and it looks like my use of
rcs commands will work, but not the intended way to work with this project.
I should have been doing the checkout of the CVSROOT project:
+ http://www.loria.fr/~molli/cvs/doc/cvs_2.html#SEC18
This is perhaps why you are running into commit problems because the reason
the loginfo file is 'already locked by pubcvs' is because I probably did a $
co loginfo. The lock is an rcs lock. So, I suspect that if you do a $ ci
loginfo, you won't see this commit problem -- i.e., you'll unlock the loginfo
file.
You can flog me for not RTFM - apologies for the heartburn.
Jeff
--
Colorado Linux Users and Enthusiasts (CLUE)
http://cluedenver.org/
Jeffery Cann, President
More information about the clue-admin
mailing list