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.
What I think I am going to do, is keep two modules. The first module will track all current changes to the code, and will bloat quickly. The second will store each major revision of the code, and will bloat slowly. Each time I add a major revision to the second repo, I will delete the current module, and recreate it using the latest major revision. Thanks for your thought on this, Regards Marts > > ----- Original Message ----- > From: "Flávio Etrusco" <Flavio.Etrusco at atan.com.br> > To: "Martin Cole" <martin at martinjcole.com>; <cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook> > Sent: Wednesday, December 17, 2003 3:48 PM > Subject: RE: [cvsnt] Good way to store a MSAccess project in cvs > > > > does anyone know a way to avoid this 10Mb file > > bloating the repository. > > Unfortunately there's nothing you can do, besides using another versioning > control tool like SVN (http://subversion.tigris.org) or - cough cough - VSS > (6c and beyond). > This would indeed be an excelent improvement for CVS... > > Tony, forgive me if it's widely avaible information, but is there a > fundamental architure "feature" in CVS that makes this so hard - or > impossible - to implement? > > -Flávio >