在ClearCase中，需要CLI调用才能列出所有修订 [英] In ClearCase, need CLI invocation to list all revisions

问题描述

我正尝试添加对在 reposurgeon 中读取ClearCase存储库的支持.我已经能够弄清我认为我需要的大部分内容，但是文档中有大量令人困惑的细节，这使一个基本问题难以理解.如何在CC资源库中列出所有修订?

I'm attempting to add support for reading ClearCase repositories to reposurgeon. I've been able to puzzle out most of what I think I need, but the documentation is a massive pile of confusing details that leaves one basic question obscure. How do I list all revisions in a CC repository?

我需要的最少内容是按时间顺序排列的行序列，每行包含一个修订ID(路径，分支，修订级别)及其父修订ID.

The minimum thing I need would be a time-ordered sequence of lines each containing a revision ID (path, branch, revision level) and its parent revision ID.

应该包括对目录的修订，因为我认为推断出删除内容将需要它.如果有某种方法可以强制列出文件删除事件，则可以省略目录修订.

Revisions for directories should be included because I think I'll need that to deduce deletions. If there's some way to force a listing of file deletion events, directory revisions can be omitted.

如果我可以得到一个四列的列表，那就会更加方便:修订ID，父ID，提交者名称和时间戳.鉴于此，将报告按摩成git快速导入流几乎是微不足道的.

It would be more convenient if I could get a four-column listing: revision-ID, parent ID, committer name, and timestamp. Given this, massaging the report into a git fast-import stream would be almost trivial.

对于VOB与其他系统中的单个项目存储库之间的关系，我还不太清楚，因此，对指定的VOB"和所有VOB"的调用会受到赞赏.

I'm still a little unclear on how VOBs relate to single-project repositories in other systems, so an invocation for "specified VOB" and another for "all VOBs" would be appreciated.

这个问题有用答案的结果是，我将越狱ClearCase，解决了如何将完整的历史记录迁移到Git的问题.

The consequence of a useful answer to this question is that I will jailbreak ClearCase, solving the problem of how to migrate complete histories out of it to Git.

推荐答案

对于基本的clearcase(在Windows上)，列出修订版本可以通过两种方式完成:

For base clearcase (on windows) listing the revisions can be done in two ways:

• clearexport_ccase

• clearexport_ccase

工具 clearexport_ccase 编写一个文本文件，其中包含一个VOB(一个存储库)的大多数相关信息.据我所知，IBM没有描述该格式.

The tool clearexport_ccase writes a textfile with most of the relevant informations of one VOB (one repository). The format is not described by IBM, as far as I know.

• 您会看到全部，但看不到文件删除或文件重命名.
• 您可以看到合并操作.

cleartool历史记录

cleartool lshistory

子命令历史记录会写入文本文件(格式可以作为参数给出)，该文件似乎包含版本化元素版本的所有元信息.

The subcommand lshistory of cleartool writes text file (format can be given as parameter) which seems to contain all meta information of the versions of the versioned elements.

不清楚是否包含元素的合并信息.

Unclear is whether it contains the merge informations of elements.

使用两个输出，您不会获取版本化元素本身，而只会获取数据库路径.要从数据库检索文件，您必须使用

With both outputs you do not get the versioned elements itself but only the database path. To retrieve the file from the database you have to use cleartool get.

• 因为基本的clearcase是面向文件的，所以每个文件本身都是版本.
• 根据文件构建变更集，必须通过查看分支，标签，作者，签入消息，签入时间...来将所有版本化的文件放在一起来完成版本

• 合并是根据文件进行的，可以通过实际合并或绘制合并箭头来完成，这意味着在文件的修订树中显示合并.

• Because base clearcase is file oriented each file is versioned by itself.
• Building changesets from the file, versions must be done by putting all versioned files together by looking at branch, tag, author, checkin msg, checkin time ...

• Merging is done file wise and can be done by real merge or drawing a merge arrow, which means to show a merge in the revision tree of a file.

可以通过在文件的版本树中绘制合并箭头来更改合并.

Merging can be changed by drawing merge arrows in the version tree of a file.

此外，您还有一个配置规范，用于定义您所使用的版本元素在您的存储库视图中查看；例如他们定义了您在自己的看法.(也许在转换VOB时可以忽略它们.)

Additionally you have a config spec which defines which versioned elements you see in your view of a repository; e.g. they define which branch you see in your view. (Perhaps they can be ignored when converting a VOB.)

它存在一个 ClearCase到SVN转换器用于基本的clearcase，它将文件修订版本转换为变更集.所以这似乎是可能的.

It exists a ClearCase to SVN converter which is working for base clearcase which converts file revisions to change sets. So it seems to be possible.

这篇关于在ClearCase中，需要CLI调用才能列出所有修订的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！