>[ On Tuesday, February 15, 2000 at 09:19:13 (+0100), Frode Nilsen wrote: ]
>> Subject: Re: CVS File Locking
>>
>> I don't see how dealing with non mergeable files breaks the concurrent
>> development paradigm.
>
>Of course it doesn't break the copy-edit-merge paradigm -- it just means
>that you have to be willing and able to deal with conflicts in a
>different way than one normally would deal with them in text files.
>
>> 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.
>
>send them e-mail, telephone them, leave a post-it on their screen, fire
>them if they make changes to files not assigned to them, etc., etc.,
>etc., ad infinitum.
>
But that is the problem, each and every developer doesn't know who all the
other developers are.

>>      2. How do I get prevented to edit a file that someone else is editing.
>
>ask around, post a note to your local developer's e-mail list, etc.,
>etc., etc., ad inifitum.
>
same problem

>CVS is not a substitute for management.
>
But it is! CVS is supposed to manage a whole lot of files for me, and avoid
me from keeping av list of which files have been changed when by who for
what reason.
And it is not the task of management to know about each and every file the
developers are working with, thats what they installed CVS for!

>> What we (the ones crying for locks) want are some means to force serialised
>> work one certain file types.
>
>Then go find some tool that fulfills this requirement.  Do not use CVS
>if you don't want to be forced to assume the copy-edit-merge paradigm is
>the only one available to you.
>
This is stupid, stupid, stupid.
I love copy-edit-merge in 99% of the cases, I would be euforic (is that the
word?) if CVS could have supported that last 1% in a nice way.

a soly copy-edit-merge paradigm can only be used 100% succesfully by them
who are doing development on their own, or only using text files (in its
strictest form).
--------------------------------
Why not?

[EMAIL PROTECTED]

Reply via email to