[EMAIL PROTECTED] on 02/11/2000 10:20:40 AM
>"cvs edit" is a communication mechanism, not a locking mechanism. Multiple
>users can still declare intent to commit changes to a single file, regardless
>of whether or not it's up to date in their workspace. The same conflicts
>inherent in concurrent editing that are such a pain to resolve do not go
>away. On the other hand, edit/watch offer some benefit because the users
>are warned beforehand when a conflict is about to occur.
If "cvs edit/watch" were used with good communication (specially if it were used
with the "cvs edit -c" patch (and the forthcoming "cvs ci -c" patch)), there's
no reason to have locks in the traditional sense (assuming you could trust at
least some of your developers).
Noel
