Clearcase：如何在处理被劫持的文件时不产生垃圾？
经过大量实验后，我的团队得出结论，在快照视图中处理被劫持的文件是使用 ClearCase 版本控制的最有效方法。问题是每次更新/合并操作后都会在目录中留下大量垃圾。这些文件的扩展名为 .keep.9 或 .contrib.16。
这些垃圾使得很难查看某些文件是否是私有的，并且我们忘记将其添加到存储库中。是否可以自动删除这些文件？
看起来您无法将某些文件配置为忽略，这是所有其他版本控制系统的基本功能。
After a lot of experiments, my team concluded that working with hijacked files in a snapshot view is the most efficient way to use ClearCase version control. The problem is that after each update/merge operation it leaves a lot of garbage in the directory. These are files with extensions like .keep.9 or .contrib.16.
These garbage makes it difficult to see if some file is private and we have forgot to add it to the repository. Is it possible to automatically erase these files?
It looks like you can't configure some files to be ignored, a basic feature of every other version control system.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
.keep.x文件由cleartool update -keep生成。一种解决方案是使用
cleartool update -overwrite，这将不会生成.keep.x文件。.contrib.x由cleartool合并生成。请参阅“UCM 中刚刚交付的每个版本留下的 .contrib 文件的说明”。但总体思路是在每次更新/合并后通过 shell 命令自动查找并删除所有 .keep.x 和 .contrib.x 文件。
例如在 Windows 中：
请注意，您还有需要注意的其他临时文件：请参阅关于 ClearCase 创建的临时文件。
.keep.xfiles are generated by acleartool update -keep.One solution would be to use a
cleartool update -overwrite, which would not generate.keep.xfiles..contrib.xare generate by cleartool merge. See "Explanation of .contrib files left for every version just delivered in UCM".The general idea though is to find and remove automatically all .keep.x and .contrib.x files after each update/merge, through a shell command.
For instance in Windows:
Note that you have other temporary files you need to pay attention to: see About the temporary files created by ClearCase.