Git中明确的基线和明确的活动的等价物？ [英] Equivalent of the clearcase baseline and clearcase activities in Git?

问题描述

为了说服某些人从 Clearcase 转移到 Git ，我需要向他们展示替代 baselining 并在 activity 名称下签入/签出文档。

Git中如何实现这些功能？在这种情况下，我只看到了标记选项，但似乎对于创建版本号而非 baselining 或 activity names。

解决方案

我的旧回答很好地比较了ClearCase和Git。

什么是每个开发人员都应该知道的基本的ClearCase概念？

他们需要了解的一个重要方面是，Git存储库将与UCM ClearCase组件等效：将所有组件>存储在一个Git仓库中，就像你可以在UCM Vob中使用（集中式）ClearCase VCS一样。

一旦你意识到了，基线i就像你的git repo一样：它会引用该回购的全部内容。如果需要，您可以在其上添加标签（如完整的UCM基线），但它不是强制性的。

每个提交代表一个活动：UCM活动是一个更改集合：更改列表，这是Git提交允许您查找的内容。

To convince certain persons to shift from Clearcase to Git, I need to show them alternatives to the baselining and checking in/out documents under activity names.

How can these be achieved in Git? I only saw the tagging option coming into the picture in this scenario, but that seemed to be useful for creating version numbers rather than for baselining or activity names.

解决方案

You can read in my old answer a good comparison of ClearCase and Git.

"What are the basic ClearCase concepts every developer should know?"

They key aspect to understand is that a Git repository would be the equivalent of a UCM ClearCase component: you cannot store all components in a Git repo like you could in an UCM Vob with the (centralized) ClearCase VCS.

Once you realize that, a baseline is just like a commit of your git repo: it will reference the full content of that repo. You can add a tag on it if you want (like a full UCM baseline), but it isn't mandatory.

Each commit represents an activity: the UCM activity is a "change set": a list of changes, which is what a Git commit allows you to find.

这篇关于Git中明确的基线和明确的活动的等价物？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！