>--- Forwarded mail from [EMAIL PROTECTED] >Is it a proven thing that CVS can corrupt a binary file if no merges >are tried and no CR/LF boundary rules are broken? In other words, if >I set -kb on a binary file and then do nothing to it but commit >updates and sometimes request an old revision, keeping my sandbox in >the OS in which it was checked out, could I ever get a bad result?
I have personally kept binary files in CVS for many years. (Since before -kb was supported, but at that time all my systems were Unix boxes.) Since -kb and Windows interoperability were introduced, I have yet to hear a credible report about a binary file corruption that did not involve one of the following: - Some kind of hardware or network failure that corrupted the RCS file. - Someone did the initial checkin of the file without -kb set beforehand. >--- End of forwarded message from [EMAIL PROTECTED] _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
