From: Michael Haggerty <mhagger@alum.mit.edu>
To: Tomas Carnecky <tom@dbservice.com>
Cc: Tuomo <tuo.tie@gmail.com>, git@vger.kernel.org
Subject: Re: Another way to compare tools: is it possible to transfer full history?
Date: Tue, 28 Sep 2010 17:48:33 +0200 [thread overview]
Message-ID: <4CA20E51.1000503@alum.mit.edu> (raw)
In-Reply-To: <4CA20169.2040606@dbservice.com>
On 09/28/2010 04:53 PM, Tomas Carnecky wrote:
> (shameless plug: just this weekend I started collecting the various fast
> import/export tools and made a webpage about it:
> http://caurea.org/fast-export-import/. It's far from complete though.
> And if you know any tools that perform better than those I've listed,
> I'd be glade to update the page).
cvs2svn [1] (in particular the cvs2git [2] and cvs2bzr [3] variants,
which are part of the same project) can convert from CVS to fast-import
format. It is mature and actively maintained [4], has a lot of features
[5], help is available, and hopefully you agree that the documentation
[6,7] is well-written.
Michael
[1] http://cvs2svn.tigris.org/
[2] http://cvs2svn.tigris.org/cvs2git.html
[3] http://cvs2svn.tigris.org/cvs2bzr.html
[4] https://www.ohloh.net/p/cvs2svn
[5] http://cvs2svn.tigris.org/features.html
[6] http://cvs2svn.tigris.org/cvs2svn.html
[7] http://cvs2svn.tigris.org/faq.html
next prev parent reply other threads:[~2010-09-28 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 13:44 Another way to compare tools: is it possible to transfer full history? Tuomo
2010-09-28 14:53 ` Tomas Carnecky
2010-09-28 15:48 ` Michael Haggerty [this message]
2010-09-28 20:48 ` Jonathan Nieder
2010-09-28 20:55 ` Sverre Rabbelier
2010-09-29 11:03 ` Tuomo
2010-09-29 11:19 ` Andreas Ericsson
2010-09-29 13:03 ` Tuomo
2010-09-29 13:28 ` Andreas Ericsson
2010-09-29 13:53 ` Tuomo
2010-09-29 14:00 ` Bruce Stephens
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=4CA20E51.1000503@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=git@vger.kernel.org \
--cc=tom@dbservice.com \
--cc=tuo.tie@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).