问题描述
可以使用哪些工具从透明案例迁移到商业案例?是否可以移动历史记录?有哪些限制?
What tools are available to migrate from clearcase to mercurial? Is it possible to move history? What kind of limitations are there?
推荐答案
请不要忘记ClearCase(中央 VCS)和Mercurial(分布式 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中，没有全局时间轴，因为每个文件都是单独提交的(以文件为中心的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存储库转换为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迁移，以用于其他考虑.
这篇关于从明文库迁移到水银库的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！