CVS 修订号
当我对项目进行 cvs 状态时，我会得到不同文件的不同修订号。 这里发生了什么？ 所有文件不应该具有相同的修订号吗？
When I do a cvs status of my project I get different revision numbers for different files. What is happening here? Should not all the files have the same revision number?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
CVS 修订版号反映了该文件已更改的次数。 如果您希望整个项目保持一致，则需要使用
cvs tag承诺给所有内容一个一致的标签。The CVS revision number reflects how many times that file has been changed. If you want something consistent across a project you'll need to use
cvs tagafter committing to give everything a consistent label.不。 cvs 不像更现代的版本控制系统那样有单一的修订号。 每个文件都有自己单独的版本。 如果有任何方法可以转移到另一个版本控制系统，如 subversion、mercurial、git……就去做吧。
no. cvs does not have a single revision number like more modern version control systems. Each file has its own separate version. If there is any way you can move to another version control system like subversion, mercurial, git...do it.
CVS 没有全局修订号，它们是针对每个文件的。 （事实上，CVS 甚至没有原子提交）
CVS doesn't have global revision numbers, they are per-file. (In fact, CVS doesn't even have atomic commits)
CVS 最初是面向文件的 RCS 上的一组脚本，它从未逃脱过它的历史。 CVS 存储库是 RCS 文件的集合，这些文件在签出时按照您想要的目录结构排列，再加上一些锁定目录。 记住这一点，您就会理解（并且也许能够预见到）许多 CVS 的特性。 （后来 VCS 有了内置目录的想法，以及跨重命名的文件连续性之类的东西。）
CVS 的全局状态想法是一个标签，必须手动应用它。 这是通过标记每个 RCS 文件来完成的。 也可以在给定时间获取存储库的副本，但这不一定是一致的，因为大型提交不一定是原子的。
所以，不，文件的 CVS 修订版是存储库中的 RCS 修订版，与任何其他修订版号无关。 不要担心修订号。
CVS was originally a set of scripts over the file-oriented RCS, and it never escaped its history. A CVS repository is a collection of RCS files arranged in the directory structure you want when it's checked out, plus some lock directories. Remember that and you'll understand (and maybe be able to anticipate) a lot of CVS idiosyncracies. (Later VCS have had the idea of directories built in, as well as things like file continuity across renames.)
The CVS idea of a global state is a tag, which has to be applied manually. This is done by tagging each and every RCS file. It's also possible to get a copy of the repository at a given time, but this is not necessarily consistent, as large commits are not necessarily atomic.
So, no, the CVS revision of a file is the RCS revision in the repository, and has nothing to do with any other revision number. Don't sweat the revision numbers.