Tailor CVS -> Mercurial: Cannot get branches migrated

Brian Wallis brian.wallis at infomedix.com.au
Tue Mar 25 00:24:31 CDT 2008

On 25/03/2008, at 4:06 PM, Brendan Cully wrote:
> The convert extension is almost always preferable to tailor for  
> importing into hg. Why not give it a try?

That is what I am currently using in my test setup and it has been  
running well with automatic 2 hourly incremental updates for about 2  
months now.  But, it has three limitations that cause me problems :-

1) it cannot do just the history from 9 months ago to now, it insists  
on doing it from our CVS epoch of sometime in 2002. I can live with  
this but it does add about 1G to our repository and we just don't  
need it.

2) There seems to be no way to say "only these two branches". I don't  
need or want the other 6 and it just adds more cruft to the new  

3) It scrambles the branches. It just doesn't get it right. The  
reason is the use of cvsps to calculate changesets and in our  
repository cvsps just doesn't work it out correctly and we end up  
with a branch head that doesn't match what is in the CVS branch. The  
reason seems to be that we have had a lot of movement and even  
hacking of tags in the repository over the years.

If I cannot get tailor working I will end up using the convert  
extension as it seems to work well for our head. I'll just fake the  
branches manually in that case.

Brian Wallis
p: 3 8615 4553 | f: 3 8615 4501 | e: brian.wallis at infomedix.com.au
Level 5, 451 Little Bourke Street, Melbourne VIC 3000

More information about the Mercurial mailing list