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.
"David Somers" <dsomers at omz13.com> wrote in message news:e74kmu$hjq$1 at paris.nodomain.org... > Perhaps you could explain more of the _why_ you need to commit *very > large* > binaries into a cvs repository. The reason is simple: I want to keep revision builds in version control. Each revision build is a file ~30 MB. Recently (as *,v file has grown in size) we found that CVSNT server crashes. >> The same logic is applicable to text files. > > Again, unrealistic. > Again, what's the difference between large binary file and small text file with *large* history? Large, grown-up projects take many of years of development and generate very large ,v files. I know one which was started in 1984 and is still in development. It was moved from RCS to ClearCase in 2001 because history processing took too much time. (BTW, CVSNT has the same/bad time processing dependency from length of the history).