From: Christian MICHON <christian.michon@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Michael Haggerty <mhagger@alum.mit.edu>,
Rostislav Svoboda <rostislav.svoboda@gmail.com>,
git@vger.kernel.org
Subject: Re: cvs2git migration - cloning CVS repository
Date: Tue, 3 Feb 2009 23:54:01 +0100 [thread overview]
Message-ID: <46d6db660902031454r1142082cu739a4d6186bc3d2e@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0902031348570.6573@intel-tinevez-2-302>
On Tue, Feb 3, 2009 at 1:55 PM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Tue, 3 Feb 2009, Michael Haggerty wrote:
>
>> If you do not have filesystem access to your CVS repository, you might
>> be able to clone it using CVSSuck [2,3].
>
> A substantially faster option would be to go with cvsclone:
>
> http://samba.org/ftp/tridge/rtc/cvsclone.l
>
> (in my case, cvsclone was not only faster, but it actually worked, too,
> which is more than I could say of CVSSuck).
>
fantastic, really! :)
it saves almost half a day of git-cvsimport on vim7 cvs official repository.
Dscho rulez... Kudos...
--
Christian
--
http://detaolb.sourceforge.net/, a linux distribution for Qemu with Git inside !
next prev parent reply other threads:[~2009-02-03 22:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 14:24 cvs2git migration - cloning CVS repository Rostislav Svoboda
[not found] ` <9a0027270902020707p4305d92fl1388bbfeb8a0864b@mail.gmail.com>
2009-02-02 16:05 ` Rostislav Svoboda
2009-02-03 12:45 ` Michael Haggerty
2009-02-03 12:55 ` Johannes Schindelin
2009-02-03 14:18 ` Michael Haggerty
2009-02-03 22:54 ` Christian MICHON [this message]
2009-02-03 23:02 ` Johannes Schindelin
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=46d6db660902031454r1142082cu739a4d6186bc3d2e@mail.gmail.com \
--to=christian.michon@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
--cc=rostislav.svoboda@gmail.com \
/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).