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 email@example.com.
----- Original Message ----- From: "Bertrand Denoix" <bertrand.denoix at kalimagroup.com> To: "C=E9dric Le Dressay" <cledressay at eugensystems.com> Sent: Tuesday, July 02, 2002 11:37 AM Subject: RE : [Cvsnt] using CVSNT for large binaries > If you don't keep previous versions why do you keep them in CVS? Just > another case of "when your only tool is a hammer, all screws look like > nails?" Just because we have more than 500 binaries that may change each day. Cvs is a software configuration management system not just a history of changes logger. Plus it makes everything consistent, any user on the project can easily get an up to date version without having to struggle through many different software. > > > -----Original Message----- > > We are using CVSNT for all our sources and the binaries used in our > > project. > > > > - For all the binaries we store we never need to keep previous > versions > > just the latest > > - some are quite large (4 Mo) and as the number of versions rise cvs > > performance suffer for those files > > > > Is there away to tell cvs for those files that we just want to keep > the > > latest version ? > > or is there away to destroy intermediate versions by an "intelligent" > > batch ? > > > _______________________________________________ Cvsnt mailing list Cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs