>[ On Monday, February 14, 2000 at 03:27:11 (-0800), Paul Sander wrote: ]
>> Subject: Re: CVS File Locking
>>
>> The message that comes across from you, Greg, is that users must choose
>> either the concurrent model or the locking model, and commit to it 100%.
>> If that simply isn't feasible, then they should adopt some difficult
>> hybrid environment.
>
>Yup. And the reason is that it would be absolutely against the design
>goals of CVS to build a hybrid environment. CVS is designed to *FORCE*
>concurrent development.
I don't see how dealing with non mergeable files breaks the concurrent
development paradigm.
Couldn't someone come up with a good solution to the problem instead of
this endless argumenting:
1. How do I prevent someone from starting to edit a file that I am
editing.
2. How do I get prevented to edit a file that someone else is editing.
This is a must if you are dealing with non mergeable files, e.g. LabView,
Photoshop, VB. Because you would not like to spend the extra hours to
manually merge the concurrent changes in these files.
And yes when using branches you have to do this manual merging, but here
the win of using branches are much greater than the extra time used on
merging.
What we (the ones crying for locks) want are some means to force serialised
work one certain file types.
Hey, that would be the ultimate solution. When adding a new file the user
would, in addition to declaring the file to be binary or text, also declare
concurrent og serialised locking.
Then you could use cvs edit for thoose special cases on the concurrent
files, and serialised files would always be locked for a given user.
> If you don't like it then don't use it (and
>don't post stupid arguments about it either).
On the contrary. If you don't like what you read here, don't read it. CVS
is a system developed of and for the world community. If the community
wants CVS to move in another direction than you, that is your problem.
And since no one is talking about removing functionality I don't see your
problem at all.
--------------------------------
Why not?
[EMAIL PROTECTED]
