Hi Noel,
>This is only true 'cos CVS defaults to checking files out read-write.
Right, this might be the topic for another thread. WHY the heck the default
is the read-write? It does not bother me much, since I will not do that, I
will check out read-only. Then I use the 'edit' to make it writable. And
then commit... I will search for modified files to see if there are any
changes leftover. It works well, but I still have to do the locking for the
darn VB files...
>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.
Souns good to me, when it is going to be integrated into official CVS?
BR,
Jerzy
The first thing they don't teach you at school: "Never say never".
All the issues not related to the list please send to me in private, thanks.
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
