by GrumpyOldMan
Subversion is what CVS should have been. It's no mystery that projects are moving en masse from CVS to Subversion.
Subversion follows the same client/server model as CVS, but is a strictly better implementation. Subversion's command line tools will feel familiar to anyone comfortable with CVS, and most of the clever accessories like Tortoise and online code browers are available for Subversion. It's worth making the switch for the
23 of 33 users found the following review helpful. Was this review helpful to you? Yes | No
by Rob Heittman
Subversion was chartered specifically to create a drop-in replacement for CVS -- something that worked similarly, but was friendly to the HTTP infrastructure and addressed some key limitations like the ability to version the directory tree structure. It's done what it set out to do, it's reached a stage of maturity and ubiquity, and I've found it to work reliably and well.
Of course most of the interesting work on source control is now
12 of 13 users found the following review helpful. Was this review helpful to you? Yes | No
by mugwump
The design roots of Subversion can be traced back to the first very simplistic attempts at version control, such as SCCS and RCS. The design of it has steamrolled on from the 70's with little consideration of stable internet development methods practiced since at least the mid-eighties.
The claim is made that Subversion "just fixes CVS". And while Subversion is generally more robust and versatile than CVS, some still see it as a step
37 of 64 users found the following review helpful. Was this review helpful to you? Yes | No
Yes this is what im talking about when I define 'userfriendly' and 'fast'. SVN seems to have so many more options than CVS, which makes CVS seem useless to me. SVN seems more like a replacement. A better one.
9 of 12 users found the following review helpful. Was this review helpful to you? Yes | No
by ajdlinux
SVN is what CVS should have been - it has pretty much everything CVS has, except it's easier - no 'login' commands and CVSROOT environment variables and huge long authentication details and so on, just a simple URL.
The only problem I have with it is that when you mess up your WC SVN makes it pretty hard to fix up, but then again I don't know whether CVS or darcs or whatever does it any better.
4 of 6 users found the following review helpful. Was this review helpful to you? Yes | No
This is a response to drbrain's review, because I think he's confused about a number of issues.
* Merge-tracking (a la p4 integrate) is coming in svn 1.5, and is already mostly working on the trunk code. You can test drive it today.
* 'svn diff' now natively supports -u, -b, -w, and other things.
* You *can* set the default diff arguments in your ~/.subversion/config file.
* "Feels" slower? Some commands are
4 of 6 users found the following review helpful. Was this review helpful to you? Yes | No
by guido
Subversion is adopted rapidly around the world. Just check this graph for adoption on public Apache servers: http://subversion.open.collab.net/subversion-adoption.html. Another interesting stat (real-time open source activity) is at http://cia.navi.cx/stats/vcs. Subversion outnumbers CVS 3 to 1 and Darcs 60 to 1. Many people must see the advantages of Subversion over CVS and other version control systems.
Subversion has many advantages
3 of 5 users found the following review helpful. Was this review helpful to you? Yes | No
by zote
I think a good feature that svn need is support to shared files (external files) like it does with folders.
by drbrain
I don't see what I get out of SVN that CVS is missing. Changesets? big deal!
No built-in branch tracking ala p4's integrate. (Hidden away in the svnmerge add-on.)
Uses less-featureful diff (no -p, -b, -c, -i), and less-reliable diff3 (has given me bad merges).
Can't set default diff arguments ala CVS in a config file without writing a shell script.
Feels slower than CVS.
Can't get all the info for a
7 of 20 users found the following review helpful. Was this review helpful to you? Yes | No