All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Haggerty <mhagger@alum.mit.edu>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Rostislav Svoboda <rostislav.svoboda@gmail.com>,
	git@vger.kernel.org, cvs2svn users <users@cvs2svn.tigris.org>
Subject: Re: cvs2git migration - cloning CVS repository
Date: Tue, 03 Feb 2009 15:18:48 +0100	[thread overview]
Message-ID: <49885248.6020805@alum.mit.edu> (raw)
In-Reply-To: <alpine.DEB.1.00.0902031348570.6573@intel-tinevez-2-302>

Johannes Schindelin wrote:
> 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).
> 
> Note: it only works for anonymous access so far.
> 
> Note also: for my use case, it was necessary to edit the rlog, as those 
> brilliant geniuses included verbatim cvs logs for files they moved. *sigh*
> If you need something like that, I can give you my patched version.

Thanks for the pointer.  I just added it to the cvs2svn/cvs2git FAQ [1].

Michael

[1] http://cvs2svn.tigris.org/faq.html

  reply	other threads:[~2009-02-03 14:20 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 [this message]
2009-02-03 22:54     ` Christian MICHON
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=49885248.6020805@alum.mit.edu \
    --to=mhagger@alum.mit.edu \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=rostislav.svoboda@gmail.com \
    --cc=users@cvs2svn.tigris.org \
    /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.