Hi Tobias,
>Maybe. I don't speak for people who have commit access to CVS. If it is
>sufficiently clean (and there I have my doubts), and far enough out of my
>way, in such a way that it would not impact me in any way, I would not have
>much trouble with CVS having locks.
>
>However, if CVS changes, and I have to change my current concurrent use of
>CVS, a tool which I *specifically* picked for its concurrent features, I
>will
>be a very unhappy man...
No problem here. I don't want to screw up what is right in CVS, so
concurency will not go away, and I want the changes concerning the locks to
be "transparent" for whose who are not using them... The first is: "No
harm". Concurency will not be affected by making the locks the right way.
The way I see it it'll in fact promote the concurent model...
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
