CVS limitations

The following are the limitations of CVS

Binary File Handling: CVS is designed to work with text-based data. Changes to text-based data are captured as diffs. CVS does not keep diffs of binary data changes, and instead keeps full copies of each revision. This will increase the size of nightly tarballs and the on-server storage of the repository. We discourage the storage of binary data on our CVS servers as result.

Case Sensitivity in File and Directory Names: CVS running under linux operating system, filenames are case-sensitive; a file with the name of 'filename' is distinctly separate from a file with the name of 'Filename'. This is in direct contrast with the case insensitivity of operating systems such as Microsoft Windows. Windows would treat both of those filenames as the same file. Users of case insensitive operating systems should be careful with their filenames. This can prevent access to data in your repository for some users.

File Permissions: CVS has no reliable mechanism for the remote control of file permissions. This comes in to play most frequently when storing executable files (such as scripts) within CVS. Permissions are defined at time of file add/commit. Manual intervention is required to change file permissions after-the-fact.

File Naming Limitations: File and directory names should not contain spaces; not all platforms handle spaces well. Commonly-reserved filenames should also be avoided.

Reference: www.sourceforge.net