当我比较集成流基准时，为什么Clearcase diffbl包含开发流中的活动？ [英] Why does Clearcase diffbl include activities from my development stream when I diff integration stream baselines?

问题描述

我们正在使用Clearcase UCM，并且有一个Integration流，每个开发人员都有一个Development流。当我进行基线比较时，有时会包括开发流中的活动。自特定基线以来，是否有任何方法可以在集成流中获得活动的简单列表？

We are using Clearcase UCM and have one Integration stream and each developer has a development stream. When I do a baseline compare, activities from the development stream are sometimes included. Is there any way to get a simple list of activities in the integration stream since a particular baseline?

推荐答案

注意：在集成中流，您将主要获得交付活动，即记录从开发流进行交付期间完成的合并的活动。

Note: in the integration stream, you will mostly get deliver activities, ie activities recording the merges done during delivers from the development stream.

因此，如果您希望在集成流上完成两个基准的活动，简单的

So if you want activities from two baselines done on the integration Stream, a simple

cleartool diffbl -nmerge -act bl1 bl2

应该就足够了。

如果您以某种方式看到开发流中的活动，那意味着您正在比较 bl1 和来自开发流的 bl2 或来自合并（即贡献活动）集成的两个基准。

should be enough.
If you somehow see activities from the development stream, that should mean you are comparing bl1 from integration stream with bl2 from a development stream or two baselines from integration with merges, ie with contributing activities.

因此 -nmerge

比较两个基准流并仅报告对该流进行的活动和版本更改。

Compares two baselines on the same stream and reports only activity and version changes made on that stream.

---

要说明为什么看到没有-nmerge的那些活动，请参见 列出基准变更集或集成活动中的贡献活动

集成Stream中的活动如下所示：

An activity from the integration Stream will look like this:

集成活动跟踪由于交付或变基操作而完成的工作，因此它们分别以交付或变基前缀命名，以帮助将其与用户创建的活动区分开。

Integration activities track work completed as a result of a deliver or rebase operation, and they are named accordingly with a prefix of either deliver or rebase to help distinguish them from user created activities.

如果右键单击活动并选择Show Contributing Activities，您将看到：

If you right-click the activity and select Show Contributing Activities, you will see:

与以下相同：

 cleartool lsactivity -contrib <deliver baseline>@\pvob

或

 cleartool lsact -fmt "%[contrib_acts]p" <deliver baseline>@\pvob

同样， -nmerge 选项避免了 diffbl 列出那些有贡献的活动。

Again, the -nmerge option avoids the diffbl to list those contributing activities.

这篇关于当我比较集成流基准时，为什么Clearcase diffbl包含开发流中的活动？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！