[EMAIL PROTECTED] on 02/17/2000 02:23:30 AM
>In fact there is another way to solve the problem of facist locking. It
>could be passed to the client (gui) application. For example it would be
>quite easy to teach the WinCvs to prevent locking for some files and enforce
>locking for the others when needed. I think it could even be done using
>existign TCl macro mechanics - no coding required. It would also be good
>because only the people who actually face the problem would get the solution
>- the others don't change anything. Althought it is not as elegant as
>solving the problem once and for all on the server side, it would do it's
>job quite all right... It would be kinda wrapper on the gui side... Hmmm, I
>begin to like the idea......any comments on this one?
My first implementation of "cvs edit -c" was to wrap "cvs" and have "cvs-wrap
edit" check the editors list before proceeding with the "cvs edit". This
solution didn't afford atomic checks in the ideal sense, but it was feasible.
Noel
