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. ----- Original Message ----- From: "Paul Newton" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, December 17, 2007 2:48 PM Subject: CVS and visual classes > Hi all > > I find myself in a situation where I'm working with another developer > and he wants us to use CVS for version control but the way he has set > things up is that all the classes we work on are in a single VCX. Can > this really work ? > > I can foresee all kinds of problems, but perhaps I'm just being overly > skeptical ... > > Thanks > > Paul Newton > > [excessive quoting removed by server] _______________________________________________ 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.
