Advertisement

SVN vs CVS

Started by December 02, 2003 07:51 AM
0 comments, last by Garfong 20 years, 10 months ago
Which is better? Advantages, disadvantages? I''ve used CVS, but never SVN.
SVN:
* Has atomic changesets
* Uses an industry strength database to hold the repository(Berkeley DB)
* Uses an industry strength web server(Apache) as the preferred server component - this lets you reuse existing authentication/authorization infrastructure
* Can perform versioned renames
* Can perform versioned copies
* Has the ability to attach arbitrary metadata(properties) to versioned files and directories
* Branching and tagging are constant time operations
* Branching and tagging actually makes sense - they are normal filesystem operations
* Transmits deltas in both directions(CVS only sends deltas from the server to the client), making it more efficient
* Stores binary files as deltas in the repository(CVS stores deltas for text files and uses full-text for each revision of a binary file)
* Is aimed at fixing most of CVS'' flaws and replacing CVS as the version control of choice in the open source community
* Is written and designed by some of the original CVS developers

CVS:
* Is slightly faster than SVN(for now)

--
AnkhSVN - A Visual Studio .NET Addin for the Subversion version control system.
[Project site] [Blog] [RSS] [Browse the source] [IRC channel]
--AnkhSVN - A Visual Studio .NET Addin for the Subversion version control system.[Project site] [IRC channel] [Blog]

This topic is closed to new replies.

Advertisement