Linked by Eugenia Loli-Queru on Fri 20th Feb 2004 06:00 UTC
On Monday, the Subversion project is scheduled to release version 1.0 of their version control system, under development for several years now. Subversion was intended from its inception as the CVS replacement and it comes with many important features previously found only on commercial VCS like Perforce. It was designed for better remote performance, and it is multi-platform with a GUI/CLI front-end.
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
You point out the flaws in CVS
you have to edit, hand move files in the repository for doing what you say. That is nothing but horrible., it doesn't version the renames or moves. And why would one ever need to fiddle with those files ? With CVS you do need it, cause it has a few shortcomings.
SVN already have directory versioning, atomic commits of several files, you can rename and move files and directories.
From the client, and it's versioned.
Using a DB helps speed on large repositories, you automatically get concurrency, hot backup features, atomic commits/checkouts.
I suggest you read a bit on the subversion.tigris.org, and perhaps also the Subversion book.