sorry for late reply... we are not storing large binary files.the original file size are too small (in MB) but after lot of revision say (150) the size of same file become in GB.if we checkout same file it's size come again in MB(which is the original size). The solution what we have is delete unwanted revision not milestone build).which is not so easy task and lot of time consuming)
can anybody give me the better solution.The limitation is we have to put these binary files(original size is in MB) in cvs server? Regards Hridyesh -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, November 11, 2004 11:48 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Size problem Hridyesh Pant writes: > > 1. In our wrapper file we have mentioned *.mcp.so this type of file > always checked in as a binary .but when we check-in xyz.mcp.xml(which should > not be checked in binary) ,cvs treat this file also as a binary. That shouldn't happen. What release(s) of CVS are you running? Are you using a local repository or client/server? > 2. we are facing a size problem of binary files.The actual size of > binary files are in MB (when we checkout) ,while in cvsserver the size of > same files become in GB due to lot of revision. In each revision size of > binary file become multiple of 2. Due to this problem synchronization taking > too much time.Is there any workaround for this problem? Don't store large binary files in CVS. -Larry Jones Everything's gotta have rules, rules, rules! -- Calvin _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
