From: Anand Kumria <wildfire@progsoc.org>
To: git@vger.kernel.org
Subject: Re: cvsimport: trying to convert freebsd cvs to git
Date: Sun, 23 Dec 2007 01:47:35 +0000 (UTC) [thread overview]
Message-ID: <pan.2007.12.23.01.47.29@progsoc.org> (raw)
In-Reply-To: 20071222171801.GE15286@genesis.frugalware.org
On Sat, 22 Dec 2007 18:18:01 +0100, Miklos Vajna wrote:
> hi,
>
> recently Stefan reported that he tried to convert the freebsd cvs' src
> module to git and he failed. i tried to help him, but i failed, too.
> here are my efforts:
>
> he made the cvs available on a (relatively) fast rsync mirror at:
>
> rsync://ftp.spline.de/FreeBSD-CVS
>
> (so you don't have to use cvsup if it's a problem for you)
>
> so after mirroring it, i had:
>
> $ ls cvs
> CVSROOT/ CVSROOT-ports/ CVSROOT-src/ ports/ src/
>
A few days prior to your email, someone else asked a similar question:
Some tools you can use:
git-cvsimport (via cvsps)
parsecvs
fromcvs
cvs2svn (development branch)
There is a more detailed listing on the wiki at
<http://git.or.cz/gitwiki/
InterfacesFrontendsAndTools#head-8870e1c81cc93f9a7a7acb5e969924ee60182d6b>
If you have access to the raw ",v" files as you do, I would suggest you
try out parsecvs. It will not do incremental imports but will you a good
idea of how you can expect the converted repository to behave / act.
Anand
next prev parent reply other threads:[~2007-12-23 2:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-22 17:18 cvsimport: trying to convert freebsd cvs to git Miklos Vajna
2007-12-23 1:47 ` Anand Kumria [this message]
2007-12-23 12:06 ` David Soria Parra
2007-12-23 17:29 ` Jeff King
2007-12-23 21:13 ` Martin Langhoff
2007-12-24 3:05 ` Jeff King
2007-12-24 3:08 ` [PATCH] cvsimport: die on cvsps errors Jeff King
2007-12-24 3:21 ` Martin Langhoff
2007-12-24 12:43 ` Miklos Vajna
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=pan.2007.12.23.01.47.29@progsoc.org \
--to=wildfire@progsoc.org \
--cc=git@vger.kernel.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 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).