[ 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. If you don't like it then don't use it (and
don't post stupid arguments about it either).
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]> <robohack!woods>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
- Re: CVS File Locking Tobias Weingartner
- RE: CVS File Locking Paul Sander
- Re: CVS File Locking Tobias Weingartner
- Re: CVS File Locking Tobias Weingartner
- Re: CVS File Locking Noel L Yap
- RE: CVS File Locking Noel L Yap
- Re: CVS File Locking Noel L Yap
- Re: CVS File Locking Noel L Yap
- Re: CVS File Locking Noel L Yap
- Re: CVS File Locking Paul Sander
- Re: CVS File Locking Greg A. Woods
- Re: CVS File Locking Frode Nilsen
- Re: CVS File Locking Greg A. Woods
- Re: CVS File Locking Frode Nilsen
- Re: CVS File Locking Kate Ebneter
- Re: CVS File Locking Frode Nilsen
- Re: CVS File Locking Tobias Weingartner
- Re: CVS File Locking Frode Nilsen
- Re: CVS File Locking Greg A. Woods
- Re: CVS File Locking Tobias Weingartner
- Re: CVS File Locking (getting... Frode Nilsen
