Re: Locking support

[Noel L Yap]

>> I still think a good process would include use of the patches to
>> support more confidence in concurrent development.
>
>My initial reaction is that either your process works, or you
>developers need training, or your process needs changing.  But I guess
>there's room for a fourth option, "You're using the wrong tools".

Well, think about it, if actual concurrent development occurs rarely, then
there's not much harm in telling users right away that there's someone else
editing the file.  Also, this process works for both non-mergable and mergable
files whereas the usual way may cause problems with non-mergable files.

Oh, yeah, regarding changing "cvs edit" so that it enforces mandatory locks,
"cvs ci" will also need to enforce them.  Even then, nothing really prevents
users from circumventing the system (even when using straight RCS).

Noel




This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan Chase & Co., its
subsidiaries and affiliates.