Wow, Greg meets his match ...
Bryon, Consider this: 3 developers (A,B,C) need to fix file X. A is making some major changes, adding lots of new functionality. B and C need to make a minor tweak to the file. In a CVS model: B anc C can be done and outa there in minutes and essentially forget about it. DONE. They are moving onto bigger and better things. X does an update and B and C's code is meged in automagically and there are no regressions. VERY COOL. In a lock while you work model. B and C need to wait for X to be done. This is very disruptive since B and C may need to work on somthing else big and their stuck waiting for X to finish or else they can change the code and potentially merge into X's code at some later time. There are issues with both models. Most people (including myself) feel that the issues relating to the CVS model are far fewer and less intrusive than the lock while you work model. I'm not saying you're wrong. However, I am saying I would find it very working with you on the same sources if you didn't choose CVS. There is a case where Greg would agree with you and that's in the case of binary files or files that can't be merged automagically - like jpegs or pngs. I STILL like the CVS model since in many cases these kinds of conflicts happen with process problems and not versioning problems - but that is a rEAlly long discussion that we don't need to get into. Good luck. G -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Greg A. Woods Sent: Friday, October 12, 2001 9:14 AM To: [EMAIL PROTECTED] Cc: CVS-II Discussion Mailing List Subject: Re: CVS - setup reserved checkout [ On Friday, October 12, 2001 at 00:06:34 (-0400), Bryon Lape wrote: ] > Subject: Re: CVS - setup reserved checkout > > *********** REPLY SEPARATOR *********** > > On 11/10/2001 at 23:03 [EMAIL PROTECTED] wrote: > > > > >Read Berliner's whole paper. Understand what it means to "force" > >developers to use a "parallel" development paradigm and learn what the > >benefits are. > > I understand it, there aren't any. Sorry you feel that way -- many people. myself obviously included, find the parallel development paradigm almost invaluable. I happen to also like the way CVS forces it on its users, though many other less purposeful tools employ the same paradigm with less forcefulness (and many of them are very successful commercial tools -- people are choosing the parallel development paradigm with their pocket books too!). -- Greg A. Woods +1 416 218-0098 VE3TCP <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]> _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs