Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Do not forget that ClearCase (<strong>Central</strong> VCS) and Mercurial (<strong>Distributed</strong> VCS) are very different.<br> See <a href="https://stackoverflow.com/questions/645008/what-are-the-basic-clearcase-concepts-every-developer-should-know/645771#645771">Core ClearCase concepts</a> for a full list. </p> <p>In the case of a migration, that means you are dealing with a <em>repository-centric</em> VCS (Mercurial) which implies "working with timelines" (a timeline being a commit, building a new changeset)<br> In ClearCase though, there is no global timeline, as each <em>file</em> is committed individually (file-centric VCS). </p> <p>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.<br> And repeat the process until the most recent label/baseline. </p> <p>The idea is: there is often no need to import the <em>all</em> history of <em>all</em> the files when migrating from ClearCase to another (D)VCS. Only the "significant" changes need to be recorded.<br> I would not recommend the "<a href="http://www.selenic.com/mercurial/wiki/ClearCaseConversion" rel="nofollow noreferrer">Conversion of ClearCase repo to Mercurial</a>" article, especially for large and old ClearCase repositories.</p> <p>See also <a href="https://stackoverflow.com/questions/542479/what-is-the-best-strategy-when-migrating-from-clearcase-to-svn">SVN migration for other considerations</a>.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload