ClearCase Conversion To Mercurial

[ndowd]

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?


Paul Franz-4 wrote:
> 
> The approach that I am planning on is to grab the source at certain 
> points (i.e. labels/tags) and then blast it into Mercurial and tagging 
> it.  (ie. find . -type f -exec hg add {} \; )
> 
> Will this work or do I need to be smarter? Does Mercurial log a change 
> when a file has been modified but no change has occured?
> 
> Note: I understand that I will need to detect file removals between the 
> labels/tags. But I want to make sure that I don't also have to do a 
> comparison on the files.
> 
> Paul Franz
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
> 
> 

-- 
View this message in context: http://www.nabble.com/ClearCase-Conversion-To-Mercurial-tp21782981p21812919.html
Sent from the Mercurial mailing list archive at Nabble.com.