[ 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.
> 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.
CVS is not a substitute for management.
> 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.
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]> <robohack!woods>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
