From: Johannes Sixt <j.sixt@viscovery.net>
To: Paul Gardiner <osronline@glidos.net>
Cc: git@vger.kernel.org
Subject: Re: Any tricks for speeding up cvsps?
Date: Fri, 08 Feb 2008 10:57:09 +0100 [thread overview]
Message-ID: <47AC2775.5090403@viscovery.net> (raw)
In-Reply-To: <47AC1FDC.9000502@glidos.net>
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
next prev parent reply other threads:[~2008-02-08 9:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 9:24 Any tricks for speeding up cvsps? Paul Gardiner
2008-02-08 9:48 ` Karl Hasselström
2008-02-08 12:02 ` Michael Haggerty
2008-02-08 9:57 ` Johannes Sixt [this message]
2008-02-08 10:11 ` Paul Gardiner
2008-02-08 10:33 ` Johannes Sixt
2008-02-09 8:32 ` Paul Gardiner
2008-02-08 12:23 ` Johannes Schindelin
2008-02-08 12:24 ` Jakub Narebski
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=47AC2775.5090403@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=osronline@glidos.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).