与CVS相比，使用SVN有什么优势？ [英] What are the advantages of using SVN over CVS?

问题描述

我的公司正在使用CVS作为我们事实上的源代码控制标准。但是，我听说很多人都说SVN更好。

My company is using CVS as our de-facto standard for source control. However, I've heard a lot of people say that SVN is better.

我知道SVN较新，但除此之外，我不知道它的好处。

I know SVN is newer, but other than that, I'm unfamiliar with its benefits.

我正在寻找的是对这两个系统的良好而简洁的比较，并指出了Java / Eclipse开发环境中每个系统的优点或缺点。

What I'm looking for is a good, succinct comparison of the two systems, noting any advantages or disadvantages of each in a Java/Eclipse development environment.

推荐答案

CVS仅逐文件跟踪修改，而SVN则将整个提交作为新修订进行跟踪，这意味着它更容易了解您的项目历史。再加上所有现代源代码控制软件都使用修订的概念，因此从SVN迁移比从CVS迁移要容易得多。

CVS only tracks modification on a file-by-file basis, while SVN tracks a whole commit as a new revision, which means that it is easier to follow the history of your project. Add the fact that all modern source control software use the concept of revision so it is far easier to migrate from SVN than it is from CVS.

还有一个原子提交问题。虽然我只遇到过一次，但是可能有2个人在CVS中一起提交可能会相互冲突，丢失一些数据并使您的客户端处于不一致状态。尽早发现这些问题并不重要，因为您的数据仍在某个地方，但是在压力很大的环境中可能会很痛苦。

There is also the atomic commit problem. While I only encountered it once, it is possible that 2 people committing together in CVS can conflict each other, losing some data and putting your client in an inconsistent state. When detected early, these problems are not major because your data is still out there somewhere, but it can be a pain in a stressful environment.

最后，围绕CVS开发的工具并不多不再。虽然像Git或Mercurial这样的新工具确实还缺少工具，但是SVN在任何系统上都有相当大的应用程序。

And finally, not many tools are developed around CVS anymore. While the new and shiny-new tools like Git or Mercurial definitely lack tools yet, SVN has a pretty large application base on any system.

EDIT 2020 ：严重，这个答案现在12岁了。忘记SVN，像其他人一样使用Git！

EDIT 2020: Seriously, this answer is 12 years old now. Forget SVN, go use Git like everyone else!

这篇关于与CVS相比，使用SVN有什么优势？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！