git 与 subversion
我正在寻找证据来说服客户从 subversion 切换到 git 来处理它必须管理的大型源代码。 在对这个主题进行了几周的彻底研究后，我个人确信 git 的好处，我还在一些较小的私人项目中使用过它，这些项目确实表现出色。 我的客户可能会更相信客观的金钱利益，而不是我的个人轶事。是否有任何版本控制研究程序的研究可以客观地展示 svn 替代方案的好处？
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 control studies programs that can show the benefits of alternatives to svn in an objective way?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
每个功能团都有一个健康的分支是可能的。如果使用 svn 就更难了。好处如下：
https://plus.google.com/109096274754593704906/posts/R4qkeyRadLR
（请务必阅读评论）
速度非常重要。事实上，您的大部分工作都是在本地工作，因此您获得了很大的生产力。
三向合并与无基础合并。在 SVN 中，当您遇到合并冲突时，无法知道基础是什么。这使得分支和合并变得非常痛苦。 GIT 则不然。
还有很多其他的。但这应该是一个好的开始。
希望这有帮助。
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.