From: David Soria Parra <sn_@gmx.net>
To: git@vger.kernel.org
Subject: Re: cvsimport: trying to convert freebsd cvs to git
Date: Sun, 23 Dec 2007 13:06:05 +0100 [thread overview]
Message-ID: <fklivc$cio$1@ger.gmane.org> (raw)
In-Reply-To: <pan.2007.12.23.01.47.29@progsoc.org>
> 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.
ParseCVS works out fine with the PHP repository for us while cvsimport
has some problems with branches. For me it looks like doing parsecvs on
an existing repository tries to check all ,v files but in fact producing
a more or less incremental update.
If you try to use parsecvs make sure that your branchname doesnot
contain / or ~ as this will cause an error on parsecvs. If you need it,
we have a simple patch for that with a small workaround on that.
next prev parent reply other threads:[~2007-12-23 12:07 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
2007-12-23 12:06 ` David Soria Parra [this message]
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='fklivc$cio$1@ger.gmane.org' \
--to=sn_@gmx.net \
--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).