你知道关于版本控制系统 (git/mercurial/svn/cvs) 的一篇好的赞成/反对论文吗? [英] Do you know of a good pro/con paper on Version control system (git/mercurial/svn/cvs)?

查看:30
本文介绍了你知道关于版本控制系统 (git/mercurial/svn/cvs) 的一篇好的赞成/反对论文吗?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

似乎很难找到关于这些版本控制系统优缺点的好的参考资料.

It seems to be quite hard to find good references about the pros and cons of these Version control systems.

如果有人可以写一篇简短而整洁的论文,将其镜像并张贴在这里,我想很多人会不那么困惑.

If someone can make a short and neat paper about it, mirror it and post it here, I think a lot of people would be less confused.

我应该使用什么版本控制系统?我认为这取决于项目和从事该项目的人数.但是也有一些普遍接受的事实,例如:Git 是最快的,CVS 是稳定且经过测试的,SVN 很简单,Mercurial 似乎对 Windows 更友好.

What version control system should I use ? I think it depend on the project and on the number of people working on it. However there are some commonly accepted facts, for instance: Git is the fastest, CVS is stable and tested, SVN is simple and Mercurial seems more Windows friendly.

此外,论文应提供证据、基准链接和每个陈述的解释.

Moreover, the paper should present evidences, link to benchmarks and explanation for each statement.

我在 stackoverflow 上写过文章,因为这里的大多数读者应该是有经验的程序员,并且知道从哪里请求获得适当的贡献或者甚至写论文(那太棒了).

I've written on stackoverflow because most of the readers here should be experienced programmers and know where to ask to get proper contributions OR even write the paper (that would be awesome).

注意:这个问题不是关于一种工具相对于另一种工具的优点(有很多关于这些主题的帖子),而是更多关于可用于区分它们并用于为您的项目选择一个的客观标准.

Note: This question is not about the relative merits of one tool over another (there are many post on those topics), but more about the objective criteria which can be used to differentiate them and used to choose one for your project.

推荐答案

DVCSAnalysis 是一个好的开始.
(好吧,Scott Chacon,Git 冠军GitHub 背后的人之一,在评论中不同意:

The DVCSAnalysis from Google is a good start.
(Well, Scott Chacon, Git champion and one of the guys behind GitHub, disagree in the comments:

这个分析已经过时了,实际上在发布时已经过时了.请参阅我的 关于 ycombinator 的评论
我的观点是 Git 和 Mercurial 在几乎所有方面都优于 SVN/CVS——我认为几乎每个以任何有意义的方式使用过这两个系统的开发人员都会同意.

This analysis is out of date, and was in fact very out of date when it was posted. See my comments on ycombinator about it
My opinion is that Git and Mercurial are superior in nearly every way to SVN/CVS - I think almost every developer who has used both systems in any meaningful way would agree.

至于 Git/Hg,它们在很大程度上具有可比性,两者都是不错的选择,尽管 Git 似乎有一点市场份额优势,FWIW.

As to Git/Hg, they are largely comparable and either would be a good choice, though Git seems to have a bit of a market share advantage, FWIW.

关于该市场份额的任何来源/参考资料,斯科特?
也许是在社交编码协作网站中声明的存储库/用户数量?

)

除此之外,我还写了一些关于该主题的一般性帖子:

Beside that, I have written some general posts on the topic:

  • differences between DVCS and CVCS
  • basic VCS concepts (about ClearCase but can be used to illustrates various differences between CVCS and DVCS)

那些 SO 答案可能不够特定于工具",但至少可以为您指出这些版本控制系统的每一类提供的相关功能.

Those SO answers may not be "tool-specific" enough, but at least can point you to the relevant features each class of those Versioning system provide.

在基准测试方面,您有 有趣的Jakub Narębski 关于网络基准测试的问题,以及 他对 Git 的回答.
这可能过于以 Git 为中心",但也可用于在决定您的项目需要哪种版本控制工具时提出正确的问题.

On the benchmark front, you have the interesting question from Jakub Narębski on network benchmarking, as well as his answer for Git.
That may be too "Git-centric", but can also be used to ask the right questions when deciding what kind of versioning tool you want for your project.

这篇关于你知道关于版本控制系统 (git/mercurial/svn/cvs) 的一篇好的赞成/反对论文吗?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆