git vs. subversion [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 11 years ago.

I'm looking for ammunition to convince a customer to switch from subversion to git for handling the large source code it has to manage. I'm personally convinced of the benefits with git after researching the topic quite thoroughly for a a few weeks, I have also used it in a few smaller private projects where it really shone. My customer will likely be more persuaded by objective monetary benefits than my personal anecdotes. Are there any studies of version contro开发者_如何转开发l studies programs that can show the benefits of alternatives to svn in an objective way?

---

A healthy branch per feature regiment is possible. It would be much harder with svn. The benefits are here:

https://plus.google.com/109096274754593704906/posts/R4qkeyRadLR (make sure to read the comments)

Speed is very significant. The fact that you are working locally for most of your work, you gain a lot of productivity.

3-way merge vs. baseless merging. In SVN there is no way to know what the base is when you are in a merge conflict. This makes branching and merging a huge pain. Not so with GIT.

There are many others too. But this should be a good start.

Hope this helps.