[EMAIL PROTECTED] on 02/12/2000 12:48:27 PM
>On Saturday, February 12, "Win32 M$" wrote:
>>
>> Nope - just the simple attribute change will solve the problems. The file
>> locked will be readonly for all axcept the locking person. After the lock is
>> released the file is readonly again - so to make changes you would have to
>> change manually the attributes.
>
>Great, what if I have a file checked out, but not locked. Now, the next person
>wants to check it out, and lock it. They do so. Now CVS (or another tool)
would
>need to go around, and modify attributes, etc, in every sandbox. How do you
know
>that certain sandboxes are stale, and not used anymore? What if I 'rm -rf
sanbox'
>before this lock?
This is only true 'cos CVS defaults to checking files out read-write. When
using "cvs edit" and "cvs watch", files are checked out read-only. Upon "cvs
edit file", the file becomes read-write. "Locks" are done by doing "cvs edit -c
file" which checks to see if anyone else is editing the file. If one presumably
has contacted the other editor and wants to proceed with concurrent development,
one does "cvs edit -f file". Both worlds are satisfied.
Noel
