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.
Bo, A commit should only be interested in the head revision so it's not too complex. We are aware of a couple of bugs with large files and also Unicode UCS-2 files on Windows. We have some patches with customers at the moment but feedback is a little varied, I suspect it still needs more work. The actual bug appears to be in the Microsoft C runtime library (malloc etc), so only affects windows - not linux or unix. However it affects what Tony calls "Corner Cases" not the everyday stuff most users do. Regards, Arthur Barrett -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Bo Berglund Sent: Saturday, 3 March 2007 6:18 PM To: cvsnt at cvsnt.org Subject: Re: [cvsnt] CVS bug - memory allocation error On Sat, 3 Mar 2007 07:37:49 +1100, "Arthur Barrett" <arthur.barrett at march-hare.com> wrote: >Georgi Kalojanov, > >A 22Mb file is tiny - there should be no problem. > >What is the CVSNT encoding of the file? Ie: is it -ku? If you don't >know then do a "cvs status" and send the results. > But doesn't the size of the RCS file (600 Mb) factor into this? In my experience when RCS files get above a few hundred Mb performance of CVSNT drops considerably. HTH /Bo (Bo Berglund, developer in Sweden) _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt cvsnt downloads at march-hare.com https://www.march-hare.com/cvspro/en.asp#downcvs @CVSNT on Twitter CVSNT on Facebook