Re: Controlling project version

Chris wrote:

That's odd since this is one of the major advantages that Subversion has over CVS (for me at any rate). When you branch or tag in CVS it will sit there and create a copy of every single file in the repository. Depending on the size of your projects this can take a while.

Maybe it's just the whole structure thing I don't understand: http://svnbook.red-bean.com/nightly/en/svn.tour.importing.html#svn.tour.importing.layout If you already have your project in subversion, how do you branch it? Compare that to: cvs tag -b "branch name" module_name ;)

Ok, this is where you need to understand the fundamental difference between how CVS and Subversion work. For CVS branching and tagging are operations in themselves. In Subversion they're just copies. How you layout your repository is up to you, but the recommended layout is usually used because you need somewhere in the repository to put branches and tags. As for how to do it... think of it as simply copying files and it should make sense... svn copy svn+ssh://server/repos/trunk svn+ssh://server/repos/tags/mytag So, that wasn't too hard was it? It's different to CVS, and it does require that you think about your repositories in a slightly different way, but to me it's a lot more flexible and it's definitely more efficient than CVS. But it's all down to personal choice. -Stut -- http://stut.net/