从 clearcase 迁移到 mercurial [英] Migrating from clearcase to mercurial

查看:24
本文介绍了从 clearcase 迁移到 mercurial的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

有哪些工具可以从 clearcase 迁移到 mercurial?历史可以移动吗?有哪些限制?

What tools are available to migrate from clearcase to mercurial? Is it possible to move history? What kind of limitations are there?

推荐答案

不要忘记 ClearCase (Central VCS) 和 Mercurial (Distributed VCS) 是非常不同的.
请参阅核心ClearCase概念获取完整列表.

Do not forget that ClearCase (Central VCS) and Mercurial (Distributed VCS) are very different.
See Core ClearCase concepts for a full list.

在迁移的情况下,这意味着您正在处理以存储库为中心 VCS(Mercurial),这意味着使用时间线"(时间线是提交,构建新的变更集)
但在 ClearCase 中,没有全局时间线,因为每个 file 都是单独提交的(以文件为中心的 VCS).

In the case of a migration, that means you are dealing with a repository-centric VCS (Mercurial) which implies "working with timelines" (a timeline being a commit, building a new changeset)
In ClearCase though, there is no global timeline, as each file is committed individually (file-centric VCS).

因此,对于迁移,您需要使用配置规范设置 ClearCase 动态视图,您将更改为列出所有相关的ClearCase 时间线"(非 UCM 视图的标签,甚至更好:UCM 视图的基线)并导入该视图将状态固定为 Mercurial.
并重复该过程直到最近的标签/基线.

So for a migration, you need to setup a ClearCase dynamic view with a config spec you will change to list all relevant "ClearCase timelines" (labels for non-UCM views or even better: baselines for UCM views) and import that fixed state into Mercurial.
And repeat the process until the most recent label/baseline.

这个想法是:当从 ClearCase 迁移到另一个 (D)VCS 时,通常不需要导入 all 文件的 all 历史记录.只需要记录重大"变化.
我不推荐ClearCase repo 到 Mercurial 的转换"文章,尤其是对于大型和旧的 ClearCase 存储库.

The idea is: there is often no need to import the all history of all the files when migrating from ClearCase to another (D)VCS. Only the "significant" changes need to be recorded.
I would not recommend the "Conversion of ClearCase repo to Mercurial" article, especially for large and old ClearCase repositories.

另请参阅 SVN 迁移以了解其他注意事项.

这篇关于从 clearcase 迁移到 mercurial的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆