CVS import: testers wanted

[Chris Morgan]

I should be able to do some testing this week, getting cvsps built on  
solaris is hassle I don't need

Chris

Sent from my iPhone

On Apr 6, 2008, at 5:13 AM, "Frank A. Kingswood" <frank at kingswood-consulting.co.uk 
 > wrote:

> Hallo!
>
> I have recently been working on a built-in version of cvsps, so that
> Mercurial can import from CVS without requiring an external cvsps, and
> without some of the bugs that cvsps has.
>
> With a built-in cvsps it also became possible to add some features, it
> now can mark branches as merged based on magic tags in cvs log  
> messages.
>
> It would be really helpful if some people here could try it, and  
> report
> back any problems or successes. I have tried it on some small and  
> really
> huge private repositories I have access to, and a couple of public  
> ones
> with more success than I ever had with cvsps-2.1 or tailor.
>
> The builtin cvsps code should be at least as good as cvsps-2.1 or  
> one of
> the unofficial post-2.1 hacked versions. It will successully import
> branched histories, including tags.
>
> That said, it will fail if you have a particularly badly borked
> repository. For example, it will may move tags to the most recent
> changeset that has a tag on a file (this can happen if you re-tag some
> files later). It will also not detect simultaneous interleaved commits
> which you may have on a very busy repository, and import the  
> individual
> pieces instead of complete changesets.
>
> There is no danger to your CVS repository because the builtin cvsps  
> code
> only ever issues 'cvs rlog' commands, and never needs to touch the
> repository files directly.
>
> The cvs import patch can be found in the mercurial-devel archives:
> http://www.selenic.com/pipermail/mercurial-devel/2008-April/ 
> 005743.html
> It applies cleanly to crew.
>
> Frank
>
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial