From: Michael Haggerty <mhagger@alum.mit.edu>
To: "Karl Hasselström" <kha@treskal.com>
Cc: Paul Gardiner <osronline@glidos.net>, git@vger.kernel.org
Subject: Re: Any tricks for speeding up cvsps?
Date: Fri, 08 Feb 2008 13:02:35 +0100 [thread overview]
Message-ID: <47AC44DB.1000002@alum.mit.edu> (raw)
In-Reply-To: <20080208094812.GA9666@diana.vm.bytemark.co.uk>
Karl Hasselström wrote:
> 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.
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
next prev parent reply other threads:[~2008-02-08 12:03 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 [this message]
2008-02-08 9:57 ` Johannes Sixt
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=47AC44DB.1000002@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=git@vger.kernel.org \
--cc=kha@treskal.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.