Re: What is the best way to convert a multi module CVS repository to git?

> Hi,
> I have inherited a rather big, old, multi-module CVS repository which I
> want to convert to GIT.
> Most of the CVS modules do belong to one project now, i.e. the
> separation into multiple modules is something of a historical accident
> now. This means it does not make sense to put each CVS module into an
> own GIT project and use submodules.
> Furthermore the conversion will be one-way, i.e. afterwards the CVS repo
> will be shutdown forever and moved to offline storage. Incremental
> conversion is therefore not an issue.
> If I need one day to convert everything (the repo is about 3GB), so be
> it - the most important feature to me is correctness (I do NOT want to
> have to run manual verifications for N days/weeks/months, just to verify
> that everything was converted), and ideally even the possibility of
> re-creating the history of files which were moved across directories
> (this HAS happened sometimes - I did not fiddle around with the RCS
> files, but used straight rm+add, and accepted the loss of history forced
> on me by CVS).
> 
> What is the best (i.e. most trustworthy) method of conversion? For now
> it seems to me that cvs2git (the ...2git companion to cvs2svn) is the
> best choice (because it can handle multi-module projects in a sane way)
> - but I'm open to suggestions!