From: Michael Haggerty <mhagger@alum.mit.edu>
To: Alex Bennee <kernel-hacker@bennee.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Truncating and cleaning a imported git repositary to make it more usable
Date: Sat, 29 Mar 2008 18:51:56 +0100 [thread overview]
Message-ID: <47EE81BC.4020700@alum.mit.edu> (raw)
In-Reply-To: <1206707716.9819.15.camel@malory>
Alex Bennee wrote:
> I've succeeded in porting our whole CVS repository into git (with plenty
> of swap, cvsps is very memory hungry). [...]
It sounds like you are doing a one-time conversion. If so, please
consider using cvs2svn [1], which can also convert to git [2].
cvsps-based tools are known to have problems with most nontrivial CVS
repositories (the contents of the output repository simply don't agree
with those of the CVS original). IMO, the only reason to use a
cvsps-based tool is if you really need incremental conversions *and* are
willing to live with data loss.
Before you trust your new repository, please make some checks. As a
minimum, make sure that the contents of each tag and branch tip revision
is the same as the contents that you get if you check out of CVS. (I
bet they don't!)
Michael
[1] http://cvs2svn.tigris.org
[2] http://cvs2svn.tigris.org/cvs2git.html
prev parent reply other threads:[~2008-03-29 17:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 12:35 Truncating and cleaning a imported git repositary to make it more usable Alex Bennee
2008-03-28 12:50 ` Avery Pennarun
2008-03-28 13:08 ` Alex Bennee
2008-03-28 15:52 ` Alex Bennee
2008-03-28 16:03 ` Alex Bennee
2008-03-28 16:43 ` Johannes Sixt
2008-03-28 18:07 ` [PATCH] Documentation: Another example for git-filter-branch Alex Bennee
2008-03-28 20:44 ` Truncating and cleaning a imported git repositary to make it more usable Mike Hommey
2008-03-29 13:47 ` Alex Bennee
2008-03-29 14:30 ` Jakub Narebski
2008-03-31 6:17 ` Johannes Sixt
2008-03-28 18:08 ` Jeff King
2008-03-28 18:19 ` Jeff King
2008-03-29 17:51 ` Michael Haggerty [this message]
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=47EE81BC.4020700@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=git@vger.kernel.org \
--cc=kernel-hacker@bennee.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).