From: Jakub Narebski <jnareb@gmail•com>
To: Florian Weimer <fweimer@bfk•de>
Cc: git@vger•kernel.org
Subject: Re: What to do if git-cvsimport/cvsps hangs?
Date: Thu, 13 Dec 2007 17:56:02 -0800 (PST) [thread overview]
Message-ID: <m3sl26qbth.fsf@roke.D-201> (raw)
In-Reply-To: <824peojm4g.fsf@mid.bfk.de>
Florian Weimer <fweimer@bfk•de> writes:
> This is probably more of a cvsps question than a GIT question, but
> AFAICT, the cvsps upstream is mostly inactive these days.
>
> I tried to import the PostgreSQL repository, using
>
> git-cvsimport -d :pserver:anoncvs@anoncvs•postgresql.org:/projects/cvsroot -k -C pgsql pgsql
>
> However, after a bit of activity, git-cvsimport hangs at the following
> line
>
> cvs rlog: Logging pgsql/src/win32
>
> strace doesn't show any system call activtiy in the cvsps process
> (which consumes 100% CPU). cvsps is Debian's 2.1-2 version.
>
> Is there some kind of replacement for cvsps which works more reliably?
You can try set of patches to cvsps there (see GitLinks at Git Wiki,
or git-cvsimport entry at InterfacesFrontendsAndTools)
http://ydirson.free.fr/en/software/scm/cvsps.html
Or you can try other CVS importers (see InterfacesForntendsAndTools):
- parsecvs by Keith Packard, used to import X.Org, seems to be
unmaintaned, requires access to *,v files (but check out cvssuck)
- fromcvs by Simon 'corecode' Schubert, uses git-fast-import,
IIRC in Ruby
- cvs2svn has _experimental_ support for git export (git-fast-import?)
so you can try this as well.
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2007-12-14 1:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 9:30 What to do if git-cvsimport/cvsps hangs? Florian Weimer
2007-12-12 15:54 ` Andreas Ericsson
2007-12-12 15:58 ` Michael Haggerty
2007-12-14 1:56 ` Jakub Narebski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3sl26qbth.fsf@roke.D-201 \
--to=jnareb@gmail$(echo .)com \
--cc=fweimer@bfk$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox