> > Mmm. :-/ A few things I don't like about (what I've heard about) SVN: > - Doesn't detect repository corruption
Not actively but in a hosted environment where the repos are properly setup and are backed-up this isn't a big concern. Google Code also runs a custom SVN server which may or may not do this. > > - Not distributed This can be a good or a bad thing depending on how the project is structured. If the project decides to have an authoritative central source, SVN works a bit better with that model. If they want to be more spread out then a distributed system can work better. Also for trivial use, most people find SVN and SVN's model a bit easier to understand and learn. > - Merges can sometimes be difficult > This can be true, but it has been made much better with SVN's latest release (1.5). > > I'd rather use a distributed source control management (like Git or Hg) so > that working remotely doesn't require a network connection. I've merged > several branches with Git and had to resolve conflicts -- I don't know from > experience how painful (or not) that is with SVN, but I've heard that it > can > sometimes be a lousy experience. If I used Google Code, I'd probably use > Git > or Hg locally, then use git-svn or hgsvn to push up to Google's SVN repo. > Another option is to use hosting which supports your version control system of choice. If you like Git there is GitHub <http://github.com/> and if you like Mecurial (hg) there is Launchpad <https://launchpad.net/>. -Sean _______________________________________________ Mid-Hudson Valley Linux Users Group http://mhvlug.org http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug Upcoming Meetings (6pm - 8pm) MHVLS Auditorium Jun 4 - Sqeak! and eToys Jul 2 - KVM (Tenative) Aug 6 - Zenos Sep 3 - TBD
