Any tricks for speeding up cvsps?

> I'm trying to convert a huge cvs repository. I've left cvsps running
> for days. First attempt, stderr filled my disc with warnings about
> tags that couldn't be associated with any one commit, without
> producing anything from stdout. I'm now redirecting stderr to
> /dev/null, but it still just sits there producing nothing. Is
> git-cvsimport infeasible for large repositories, or are there tricks
> I might use?

> On 2008-02-08 09:24:44 +0000, Paul Gardiner wrote:
> 
>> I'm trying to convert a huge cvs repository. I've left cvsps running
>> for days. First attempt, stderr filled my disc with warnings about
>> tags that couldn't be associated with any one commit, without
>> producing anything from stdout. I'm now redirecting stderr to
>> /dev/null, but it still just sits there producing nothing. Is
>> git-cvsimport infeasible for large repositories, or are there tricks
>> I might use?
> 
> This topic comes up on the list every once in a while; try searching
> the list archives.
> 
> I seem to recall that for heavy imports, the Subversion CVS importer
> is popular. I don't know if it can give you a git repository directly,
> or if you'll have to go via svn.

> I'm trying to convert a huge cvs repository. I've left cvsps running for
> days. First attempt, stderr filled my disc with warnings about tags that
> couldn't be associated with any one commit, without producing anything
> from stdout. I'm now redirecting stderr to /dev/null, but it still just
> sits there producing nothing.  Is git-cvsimport infeasible for large
> repositories, or are there tricks I might use?

> I've used fast-export (not git-fast-export) to convert a CVS repository:
> 
> http://repo.or.cz/w/fast-export.git
> 
> It worked better than git-cvsimport because the repository was a real mess.

> Johannes Sixt wrote:
>> I've used fast-export (not git-fast-export) to convert a CVS repository:
>>
>> http://repo.or.cz/w/fast-export.git
>>
>> It worked better than git-cvsimport because the repository was a real
>> mess.
> 
> That looks to require going either via svn or mercurial. Is that right?
> And if so, which did you find best?

> Paul Gardiner schrieb:
>> Johannes Sixt wrote:
>>> I've used fast-export (not git-fast-export) to convert a CVS repository:
>>>
>>> http://repo.or.cz/w/fast-export.git
>>>
>>> It worked better than git-cvsimport because the repository was a real
>>> mess.
>> That looks to require going either via svn or mercurial. Is that right?
>> And if so, which did you find best?
> 
> You are right. Because I'm utterly confused. I actually used fromcvs/togit:
> 
> http://ww2.fs.ei.tum.de/~corecode/hg/fromcvs
> 
> Please bear with me; I did this about a year ago. Sorry for the noise.
> 
> Be warned that fromcvs/togit does not convert tags.

> I'm trying to convert a huge cvs repository. I've left cvsps running for 
> days. First attempt, stderr filled my disc with warnings about tags that 
> couldn't be associated with any one commit, without producing anything 
> from stdout. I'm now redirecting stderr to /dev/null, but it still just 
> sits there producing nothing.  Is git-cvsimport infeasible for large 
> repositories, or are there tricks I might use?

> I'm trying to convert a huge cvs repository. I've left cvsps running
> for days. First attempt, stderr filled my disc with warnings about
> tags that couldn't be associated with any one commit, without
> producing anything from stdout. I'm now redirecting stderr to
> /dev/null, but it still just sits there producing nothing.  Is
> git-cvsimport infeasible for large repositories, or are there tricks
> I might use?