Wednesday 12 October 2005 @ 3:14 pm
I’ve previously used CVS on a few projects. It is the defacto standard for version control, stable and works very well. At this point of time i have to make a decision on using CVS again or moving towards the buzzed Subversion.
It is a though decision for someone who is not fully aware of the nitty gritty things CVS and Subversion both have to offer. That is why i am calling for help!
What is Subversion?
According to the Subversion site, it is meant to be a better CVS
That looks promising! Subversion was designed from the ground up as a modern, high-performance version control system. In contrast to CVS, which had grown organically from shell scripts and RCS, Subversion carries no historical baggage.
Subversion takes advantage of a proper database backend, unlike CVS which is file based. The Subversion team have tried to make the new system similar in feel to CVS, so users are immediately at home with using it. Most of the features of CVS including tagging, branching and merging, are implemented in Subversion, along with host of new features:
- versioning support for directories, files and meta-data
- history tracking across moves, copies and renames
- truly atomic commits
- cheap branching and merging operations
- efficient network usage
- offline diff and revert
- efficient handling of binary files
Links:
- Using Subversion on Windows (tip!)
- Subversion for CVS Users (tip!)
- Experiences with Subversion/a>
- Subversion for CVS Users
Any comments on choosing Subversion in favour of CVS are highly appriciated
— By Marco Pas Comments (4) PermaLink
