仍然使用 CVS 的理由是什么？
鉴于 Subversion 基本上是为了取代 CVS 而编写的，那么目前是否有任何令人信服的理由继续使用 CVS 进行版本控制？
Given that Subversion has basically been written to replace CVS, are there any compelling reasons at this point to continue using CVS for version control?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我想扭转这个问题。 是否有令人信服的理由切换到 Subversion？ 我们使用 CVS，它对我们的东西工作得很好。 我们认为转换根本没有任何商业利益。
与所有决策一样，应该进行成本/效益分析，看看是否值得。 您的问题没有为我们提供足够的信息来帮助您。
I would turn that question around. Are there compelling reasons to switch to Subversion? We use CVS and it works fine for our stuff. There's no business benefit at all that we can see for switching.
As with all decisions, it should have a cost/benefit analysis done to see if it's worth it. Your question doesn't give us enough information to help you out there.
我听到的只有一个支持 CVS 的好论点，那就是当您的项目有许多不同的版本和分支时，在 CVS 中，将任意文件推送到分支或标记中会更容易当你需要的时候你需要它。 SVN 在这些方面更加正式，并且使得仅选择一个文件并根据需要合并它变得更加困难。 这是一件危险的事情，但就像直接内存指针一样，有时您只是需要它们。
话虽如此，如果 CVS 已经就位，情况可能会有所不同。 这里需要考虑的是转换是否有好处。 其中之一可能是 SVN 使您能够更好地在与办公室断开连接的笔记本电脑上进行编码。 您可以安排添加和删除文件，并且可以在返回办公室后签入。
有些组织不会梦想让他们的开发人员在他们的笔记本电脑上获取源代码，因此这不适用于他们。
我的观点是，SVN 应该是新项目的默认选择。 它很成熟，它的工具支持与 CVS 一样好，甚至在某些情况下更好，并且与 CVS 相比并没有任何重要的缺陷。
话虽这么说，GIT 正在兴起。 它仍然有点不成熟（例如Windows支持还没有达到成熟阶段）并且工具支持仍在迎头赶上，但是如果分布式分支对您很重要，那么值得好好看看。
There is only one good argument I've heard in favor of CVS, and that is in situations where you have a project that will have many different releases and branches, in CVS it is easier to just push an arbitrary file into the branch or tag you need when you need it. SVN is more formal about these things, and makes it harder to just pick on one file and merge it as you need it. It is a dangerous thing, but like direct memory pointers, sometimes you just need them.
That being said, if CVS is already in place, that may be a different story. There the calculus is is there a benifit in switching. One might be that SVN gives you better ability to code on your laptop disconnected from the office. You can schedule files for adding and deleting, and you can check that in when you get back to the office.
Some organizations wouldn't dream of letting their developers out with the source code on their laptop, so this doesn't apply to them.
My view is that SVN should be your default choice for new projects. It is mature, its tool support is as good as CVS, if not better in some cases, and doesn't really have any important deficiences over CVS.
That being said, GIT is up and coming. It still a little immature (for example Windows support hasn't hit the mature stage) and the tool support is still catching up, but if distributed branching is important to you, it is worth taking a good look.
是的，如果您隶属于一个不愿改变的大型组织。
如果您询问选择 CVS 作为新安装的一部分是否合适，我想不出一个好的理由。 现在我认为选择将归结为 SVN 或 GIT，并且选择将取决于哪个更适合您组织的开发策略。
Yes, if you're part of a larger organization that's reluctant to change.
If you're asking whether it would be good to choose CVS as part of a new installation, I can't think of a good reason. Now I think the choice would come down to SVN or GIT, and the choice would depend on which fit better into your organization's development strategy.