Comparison of cvs and svn

1 Support for renaming and deleting files
cvs: does not support local file renaming and submission,
delete points, remove and erase, the former deletes both local and library files, the latter only deletes local files and
cannot delete folders
svn: supports file renaming The submission system will prompt to delete the old file and create a new file.
Delete the local file and the file in the submission library will also be deleted.


2 Support for Chinese path names
cvs: better supported
svn: save the permission control file in UTF-8 format supported by svn


3 Correspondence between local files and libraries
cvs: can be many-to-many
svn: a library can have multiple working directories, but a working directory can only correspond to one library, although the library location can be changed, but the requirements are very strict


4. The file storage method in the library
cvs: Complete user visibility is exactly the same as the client folder structure (except for cvs generated files)
svn: similar to vss, you cannot see the real content of the file


5 User and rights management
cvs: it is difficult for administrators to clearly know how many projects there are What are the permissions and passwords of each user? Users can only be managed in groups, and the passwords and permissions are still unclear
. svn: view and modify configuration files . , no one can delete the folder (admin can only go to the server to delete the corresponding folder cruelly? I only know this method for the time being... Khan-_-”) svn: only read, write, none three permissions creat and Delete permission seems to be bundled with write