Remember that ClearCase ( Central VCS) and Mercurial ( Distributed VCS) are very different.
See Core ClearCase Concepts for a complete list.
In the case of migration, this means that you are dealing with a repository-oriented VCS (Mercurial), which means "working with timelines" (timeline - fixing, creating a new set of changes)
However, ClearCase does not have a global timeline, as each file is executed individually (file-centric VCS).
So, for migration, you need to set up a dynamic ClearCase view with a configuration parameter that you will change to list all relevant “ClearCase timelines” (labels for non-UCM views or even better: baselines for UCM views) and import this fixed state in Mercurial.
And repeat the process until the very last mark / baseline.
The idea is this: often there is no need to import the entire history of all files when transferring from ClearCase to another (D) VCS. Only “significant” changes need to be recorded.
I would not recommend the article Converting ClearCase repo to Mercurial ", especially for large and old ClearCase repositories.
See also SVN porting for other considerations .
VonC May 14 '09 at 4:28 a.m. 2009-05-14 04:28
source share