ClearCase Conversion To Mercurial

[Martin Geisler]

ndowd <noahdowd at yahoo.com> writes:

> I am currently trying to do the exact same thing.  I want to retain
> the commit comments for each check-in from ClearCase.  At the moment
> I'm trying to convert from CC to Subversion using the Polarion
> svnimport tool, which has worked extremely well.  svnimport puts the
> main/LATEST in /trunk, and puts each tagged version in
> /trunk/tags/mytag, and puts each branch in /trunk/branches/mybranch
> (although that structure is configurable).
>
> The problem I'm running into is then converting that into HG using
> the hg convert.  If I just run hg convert on the entire svn repo, it
> gives me the same /trunk/branches/tags structure, which makes it
> difficult to push a change to a tagged release into the latest
> development repo.  I'd like the convert to correctly tag versioned
> files so that doing a "hg clone -r mytag" will give me the correctly
> tagged release version, then make changes in the clone and push the
> changes back to the main development repo.
>
> Do I need to do as Paul is describing here, and svn co each tagged
> version, then do an hg add?  Am I missing something?

I think you should use the traditional SVN layout:

  /trunk
  /tags/mytag
  /branches/mybranch

-- 
Martin Geisler

VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multiparty Computation) to Python. See: http://viff.dk/.