Hi Vlad, > I noticed some projects(gaim for example ) already using svn on SF. Can > we switch to svn as well?
I wrote this already to the list during the SF mail problems so maybe you have it already: * SVN was developed from scratch, * the repository is based on Berkeley DB, * you don't need repository access for diffs etc., * SVN sets a new revision number for the whole project after every commit, * version control for directories (copy, move, add, delete, mkdir), * transactions with rollbacks, * more protocols to access repositories (svn, svn+ssh, file, http [apache2+webdav], https), * cheap copy when creating branches and tags (a tag is simply a "copy" of e.g. a directory hierarchy using almost no space until you branch), * nice handling of binary files (everything is "binary" and you can set/change mimetypes), * explicit setting of keywords you want to use (like "Id"). Just try "cvs2svn" or take a look here: http://www.onlamp.com/pub/a/onlamp/2005/10/03/cvs-to-subversion-with-cvs2svn.html As long as we have the CVS repos it should be safe to play with cvs2svn. We use SVN in the company since early 1.0 release and never wanted to revert back to CVS. Of course, not everything is sugar and creme, but as many things are similar to CVS you don't have to learn all too much. I recommend ISBN 3-89842-603-3. Bernd.
