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.
----- Original Message ----- From: "Bo Berglund" <Bo.Berglund at system3r.se> To: <cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook> Sent: Tuesday, June 04, 2002 5:51 PM Subject: RE: [Cvsnt] importing large module size > There are several reasons one can think of for importing binaries into CVS: > 1) The binaries are part of the graphics for the application (image files) > 2) The exe file, even though it can be built again, not everybody working > on the repository and checking out files have the development tool for > the module and still want the exact revision of the exe to test against > error reports or similar. Also for very large systems (say the software for a cell phone which typically consists of around 50 modules) it makes good sense to store a library for each module in the version control system. That way you do not have to compile the entire system (which can easily take the better part of a day), only the module that you have changed. -Torsten _______________________________________________ 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