Attic 和目录中的 CVS 逗号 -v 文件
我有一个已有多年历史的生产 CVS 存储库，并且注意到它在 Attic 和给定位置的实际目录中都有同名的逗号-v 文件。这似乎是一个错误。
我的问题是，这种情况首先是如何发生的，以及当存在重复文件时 CVS 会做什么。
我的猜测（希望）是，当存在非 Attic 版本时，它会始终忽略 Attic 版本。任何人都可以确认 CVS 在这种情况下是否始终表现良好。
顺便说一句，这个错误是由 cvs2svn 标记的，因为我正在进入“较新”的源代码控制系统。
I have a production CVS repository that is a number of years old and have noticed that it has comma-v files with the same name in both Attic and in the actual directory for a given location. This appears to be an error.
My question is how can this occur in the first place and what will CVS do when duplicate files exist.
My guess (hope) is that it will ignore the Attic version all the time when there is a non Attic version. Can anyone confirm if CVS behaves well all the time for this situation.
Incidentally, this error was flagged by cvs2svn as I'm in the process of getting into a "newer" source control system.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这个问题是由于某人在 CVS 存储库中乱搞造成的（即，不是通过 cvs 客户端）。不幸的是，这种破坏很常见，例如为了绕过 CVS 不允许重命名文件的限制。也许有人试图通过移动
FILENAME,v文件来重命名文件，但没有注意到该文件名已在项目历史记录的早期使用过，因此已经有Attic/FILENAME,v< /代码> 文件。由于这是存储库损坏的一种形式，我怀疑 CVS 在这种情况下的行为是否有记录。您的猜测很可能是正确的，但确保它始终以这种方式运行可能需要分析 CVS 源代码 - 对于您曾经使用过的所有版本的 CVS。我建议您对典型的 CVS 客户端和最重要的分支进行一些实验。
cvs2svn 有许多解决此问题的建议。
This problem results from somebody's mucking around within the CVS repository (i.e., not via the cvs client). Unfortunately, such mucking is common, for example to get around the limitation that CVS does not allow files to be renamed. Perhaps somebody tried to rename a file by moving its
FILENAME,vfile, without noticing that the filename had been in use earlier in the project's history and therefore already had anAttic/FILENAME,vfile.Since this is a form of repository corruption, I doubt whether the behavior of CVS in this situation is documented. Most likely your guess is correct, but ensuring that it always behaves this way would probably require an analysis of the CVS source code--for all versions of CVS that you have ever used. I suggest that you do a few experiments with your typical CVS client and your most important branches.
cvs2svn has a number of suggestions for working around this problem.