Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Bo Berglund wrote: >On Thu, 11 Nov 2004 22:27:37 +0100, Torsten Martinsen ><torsten at tiscali.dk> wrote: > >>We also used this approach previously, but have found that using "cvs >>import" is a superior solution - after all, cvs import was designed for >>tracking third-party sources. >> > >No, you don't understand the situation!! >There are no 3rd party sources involved at all. Instead we have many >projects that use common functionality, which we have stored in a >"Common" repository. We have utility functions and we have common >database classes and things like that. Yes, I *do* understand the situation. This is exactly the same scenario that we have. Understand that "third-party" can be relative to the *project*, not necessarily relative to the *organization*. >The real projects are stored in various other repositories, mainly >because of isolation issues when we started CVS. This precludes using >modules and modules2.... Exactly the situation we have. -Torsten