Hi Tobias,

>But yet you advocate exclusive locks?  I fail to see how the exclusive
>locking model you propose will be any different, other than in the way
>that you happen to work with it.

No, I do not advocate exclusive locks - you do! You want to keep the things 
the way it is now, I am suggesting to make an experiment and move the locks 
away, see what will happen. Life would verify is it a good move or not. I am 
very sorry if you don't see the difference between now (locks any time) and 
propsal (locks isolated, as a last-resort).

>Great, so we get rid of 'cvs admin -l', right?  That would make them 100%
>hard to turn on.  Problem solved.

100% hard is to remove. You are going to the extremes - please stop 
promoting the facist methods - facist locking is same dangerous like facist 
concurency... Life is not black and white - life is colorfull!

>But no, that would impact your current
>use of CVS too much, and as you've said (paraphrased) "you'd have to drop
>CVS as a viable tool" at that time...

As I stated before, I will not directly benefit the change. Unless in the 
next job - where I would have 10% chance to see CVS ever again, since I 
mostly works on Windows platform. However I am considering to setup the 
Linux box and CVS on it, to make some research on my own. I think the change 
will affect more people than just me - and that is why we are talking about 
it here, on this forum.

> > >I'm telling you there are better ways to handle your VB files.
> >
> > Maybe, but my VB files is only an example. I want a generic solution.
>
>I believe your original reason for jumping on the locking bandwagon was
>due to you having trouble with your VB files.  Several people on the list
>gave you solutions *using the current CVS code* to this problem.  No
>locking required.

Right, you are missing the point again... OK, one more time - we are talking 
how to get rid of the locks, and not harm CVS and it's users. I didn't start 
the thread about it - I just answered some other person question and it lit 
the fire. Why it lit the fire is because it is imprtant topic, and some 
solution have to come up sooner or later. VB files showed up when the 
request for a practical example have been made. Please review the posts...

The whole point is that current CVS code is not perfect - we look for the 
ways to make it better. You look for the ways to ignore the problem and keep 
the wrong 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

Reply via email to