Any tricks for speeding up cvsps?

Hi,

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?

P.

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.

-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle

Paul Gardiner schrieb:

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.

-- Hannes

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?

P.

Paul Gardiner schrieb:

Johannes Sixt wrote:

quoted

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.

-- Hannes

Karl Hasselström wrote:

On 2008-02-08 09:24:44 +0000, Paul Gardiner wrote:

quoted

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.

The trunk version of cvs2svn [1] can convert directly from CVS to git,
including branches and tags.  Recently I wrote up better documentation
[2] for using cvs2svn to convert to git.

Please direct suggestions, bug reports, or offers of help to the cvs2svn
mailing lists [3] or irc channel [4].

Michael Haggerty

[1] http://cvs2svn.tigris.org
[2] http://cvs2svn.tigris.org/cvs2git.html
[3] http://cvs2svn.tigris.org/servlets/ProjectMailingListList
[4] irc.freenode.net, channel #cvs2svn

Hi,

On Fri, 8 Feb 2008, 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?

The obvious thing is to have the CVS repository locally.  And then on a 
ramdisk.

Hth,
Dscho

Paul Gardiner [off-list ref] writes:

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?

Please check other tools to import from CVS; they are mentioned
on the

  http://git.or.cz/gitwiki/InterfacesFrontendsAndTools

wiki page ("Interaction with other Revision Control Systems" section)
-- 
Jakub Narebski
Poland
ShadeHawk on #git

Johannes Sixt wrote:

Paul Gardiner schrieb:

quoted

Johannes Sixt wrote:

quoted

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.

That's amazing. Less than an hour to for the initial conversion,
and just minutes to progressively sync up.

Thanks to everyone for all the usefull feedback I've received here.

Cheers,
	Paul.