阁楼和目录中的CVS逗号-v文件 [英] CVS comma-v files in Attic and directory

问题描述

我有一个生产的CVS存储库已有多年的历史，并且注意到它在给定位置的Attic和实际目录中都有同名的comma-v文件.这似乎是一个错误.

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.

我的问题是，首先如何发生这种情况?当存在重复文件时，CVS会怎么做.

My question is how can this occur in the first place and what will CVS do when duplicate files exist.

我的猜测(希望)是，当有非Attic版本时，它将始终忽略Attic版本.任何人都可以确认CVS在这种情况下是否一直表现良好.

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.

偶然地，当我正在进入较新的"源代码控制系统的过程中，cvs2svn标记了此错误.

Incidentally, this error was flagged by cvs2svn as I'm in the process of getting into a "newer" source control system.

推荐答案

此问题是由于某人在CVS存储库中混用(即，不是通过cvs客户端)造成的.不幸的是，这种处理很常见，例如为了克服CVS不允许重命名文件的限制.也许有人试图通过移动文件FILENAME,v重命名文件，却没有注意到该文件名在项目历史记录的较早版本中已经使用过，因此已经有了文件Attic/FILENAME,v.

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,v file, without noticing that the filename had been in use earlier in the project's history and therefore already had an Attic/FILENAME,v file.

我的猜测(希望)是，当有非Attic版本时，它将始终忽略Attic版本.任何人都可以确认CVS在这种情况下是否一直表现良好.

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.

由于这是存储库损坏的一种形式，因此我怀疑在这种情况下CVS的行为是否已记录在案.您的猜测很可能是正确的，但是要确保它始终以这种方式运行，可能需要对CVS源代码进行分析-对于您曾经使用过的所有版本的CVS.我建议您对典型的CVS客户端和最重要的分支进行一些实验.

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标记了此错误.

Incidentally, this error was flagged by cvs2svn as I'm in the process of getting into a "newer" source control system.

cvs2svn有许多解决此问题的建议.

cvs2svn has a number of suggestions for working around this problem.

这篇关于阁楼和目录中的CVS逗号-v文件的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！