tag:blogger.com,1999:blog-3339316202894508517.post4375341895369755772..comments2010-07-26T16:25:46.616-07:00Brian Duffhttp://www.blogger.com/profile/15591692569924908268noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-3339316202894508517.post-85400101795871354932007-05-25T03:03:00.000-07:002007-05-25T03:03:00.000-07:00Agreed with the of benefits that you listed like atomicity and folder versioning..etc.<BR/><BR/>But one thing is still missing in SVN, history across the branches in a single view. It is supported in CVS. <BR/><BR/>That's the only reason of my dislike of SVN.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3339316202894508517.post-87506199581459000242007-05-18T12:12:00.000-07:002007-05-18T12:12:00.000-07:00As alblue subsequently noted on his blog, you can now get an "official unofficial" Mac OS X build directly from <A HREF="http://downloads.open.collab.net/binaries.html" REL="nofollow">CollabNet</A>.<BR/><BR/>Prior to this, I'd been getting Subversion from one of the guys at <A HREF="http://www.codingmonkeys.de/mbo/" REL="nofollow">Coding Monkeys</A> (the SubEthaEdit people); he's done a good job of staying up to date, with 1.4.3 currently available.Russell Finnhttp://www.blogger.com/profile/07284905739653116442noreply@blogger.comtag:blogger.com,1999:blog-3339316202894508517.post-89112679766116832932007-05-10T09:19:00.000-07:002007-05-10T09:19:00.000-07:00A reason *not* to use SVN is that you can't get up-to-date binaries for the Mac. And you can't compile it because you can't check out the code from SVN.<BR/><BR/>When SVN is supported on the Mac (and by supported, I mean a binary that I can download and install), I'll switch to using it. However, at the moment, it's Linux/Windows only.AlBluehttp://www.blogger.com/profile/06362201865553416948noreply@blogger.comtag:blogger.com,1999:blog-3339316202894508517.post-7981709599153903612007-05-09T06:17:00.000-07:002007-05-09T06:17:00.000-07:00I love that you can use https to access SVN, which makes it much easier to use through firewalls. On the other hand, commits and updates are much, much slower.Genehttp://www.blogger.com/profile/08974776786387836646noreply@blogger.comtag:blogger.com,1999:blog-3339316202894508517.post-40340164600720560052007-05-08T13:45:00.000-07:002007-05-08T13:45:00.000-07:00One more reason why I like svn is that, it is not the individual files that are versioned. It is the whole project that is versioned.<BR/><BR/>This way you don't need to know a particular version of a particular file, rather you need to know, a file in the particular version of the entire project. This simplifies things a lot.Ganeshji Marwahahttp://www.blogger.com/profile/01919214182520822111noreply@blogger.comtag:blogger.com,1999:blog-3339316202894508517.post-5278639170261571262007-05-08T09:26:00.000-07:002007-05-08T09:26:00.000-07:00Pretty much the only reason to use CVS these days is because you registered a project on sourceforge before they supported Subversion, and even then, you can migrate.<BR/><BR/>I was a great fan of CVS in its day (WinCSV rules!), but it is 2007, and atomicity has to be a given....Richard Rodgerhttp://www.richardrodger.comnoreply@blogger.com