The "copy, modify, merge" functionality is the basis of both SVN and CVS.
SVN supports atomic commits, that's a feature CVS misses. It means that a commit is not visible ot the others unless executed sucessfully. Maybe he got that wrong ?
SVN does support locking of files if enabled.
Von: Mark Galbreath [mailto:GalbreathM@gao.gov]
Gesendet: Donnerstag, 23. Februar 2006 16:34
Cc: email@example.com; firstname.lastname@example.org; email@example.com; firstname.lastname@example.org
Betreff: CVS v. SVN
I've read all the literature on the svn website, and the online book at red-bean, and thought I understood the differences between CVS (a locking reporsitory) and SVN (a merging repository). Then I got into a discussion with a guy at the office I just met and he tells me I have it all backwards. Then tells me that developers can walk on each other's code with CVS, but not SVN because SVN locks write access. This is 180 degrees off from my understanding. He maintained that SVN is way better than CVS, but I got the impression he didn't know what he was talking about, and I am still too green to stand my ground in such a debate.
Received on Thu Feb 23 17:08:41 2006
This is an archived mail posted to the Subversion Users