与 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.

还有原子提交问题.虽然我只遇到过一次，但两个人在 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屋！