<i>This post was originally made by <b>skyjake</b> on the dengDevs blog. It was posted under the categories: Practices, SourceForge.</i>
I've been recently experiencing a host of issues with SF.net's Subversion service and the prospect of switching to <a href="http://git-scm.com/">Git</a>
; for version control is looking more and more attractive. I had very positive experiences with Git while working on Hawthorn, and the advantages of Git would be very beneficial at the moment.
<li>SVN is a dog when it comes to branch merge performance. It took me literally half a day to merge new-order-phase3 back to the trunk. Plus I was forced to do the final commit in several steps as the connection kept breaking. Also, SVN had somehow become confused about a couple of deleted files that had new content with the same file name (CMakeLists.txt), and was complaining about hash mismatches.
<li>I'm doing simultaneous development on three platforms (located on two separate computers), and it's a major inconvenience having to commit changes to SF.net in order to get them transferred between the systems. With Git I could just pull the changes over my private LAN, quick and easy.
<li>Being a distributed VCS, Git excels at branching. Using Git would make it so much more practical to create feature and task specific branches.
<li>Git's performance is in a different league compared to SVN. Doomsday has a fairly sizable code base already. Performance of repository operations is already an important issue, and it will become more so as time goes on.
The largest downsides of Git are increased complexity when compared to SVN and at least in the past the Windows support has been rudimentary. <a href="http://code.google.com/p/tortoisegit/">TortoiseGit</a>
; should be given a try.
Nevertheless, I'm of the opinion that we should move on from SVN and begin the era of Git. Any objections?