Grigore Thanks for your reply but ....
Grigore Dolghin wrote: > There are two models: Lock-Modify-Unlock and Copy-Modify-Merge. Both have > their strengths and weaknesses. > > I would suggest for you to use Lock-Modify-Unlock model, but this means only > one developer makes changes at a time. To keep productivity, your classlibs > should be small and containing fewer classes, to minimize the chances you > both need to open the same classlib. The problem is that the classlib is large and contains all the classes we need - I agree Lock-Modify-Unlock would be best but this is exactly the reason that I started this thread ... CVS (or Subversion ?) will lock the whole VCX if I want to work on one class he won't be able to work on any other class in the same VCX. Because of the way he has set up everything in one humongous VCX, I really I see this as a can or worms ... That would only leave us with Copy-Modify-Merge as an option ... and I'm not sure if there wouldn't be problems with that approach as well Paul Newton _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
