Actually, this quote was mis-attributed... The CVS manual online at cvshome.org has a pretty good description of how CVS directory level locking works.
--- Forwarded mail from [EMAIL PROTECTED] > Paul Sander <[EMAIL PROTECTED]> writes: > > Actually, if you look closely, I believe that CVS will not do read-only > RCS operations if a CVS write-lock exists for the directory. Of course, > ViewCVS and CVSweb do it all the time as do many of the other add-ons. I'm getting more worried about this one for 2 seperate reasons: 1) There is talk of cvs -n for diff and the like which seems to suggest it ignores locks. 2) I could do with a better under standing of the directory locks; pointers? I've read the top of lock.c but it still doesn't tell me enough; for example there seem to be multiple lock files used - but then surely the creation of them isn't atomic? Or is there one lock file used for both reading and writing? --- End of forwarded message from [EMAIL PROTECTED] _______________________________________________ Info-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/info-cvs
