We have noticed that some of our files in CVS are getting off-by-one bit errors.  For example, in a text file, an 'L' is converted into a 'K' and a space into a '1' (two bits were modified here).  This is not too bad in text files because a differencing tool will usually detect the problem, but binary files could be a more significant problem.
 
Our developers are geographically separated, so we use pserver mode where the server is accessible on the internet.  Are there any built-in CVS features or extra transmission verification methods we could use to minimize the possibility of errors in CVS?
 
Thanks,
 
- Dennis

Reply via email to