From: "Kelly F. Hickel" <kfh@mqsoftware.com>
To: <git@vger.kernel.org>
Subject: git fast-import problem converting from CVS with git 1.6.1 and cvs2svn 2.2.0
Date: Tue, 20 Jan 2009 09:46:52 -0600 [thread overview]
Message-ID: <63BEA5E623E09F4D92233FB12A9F794302BC6851@emailmn.mqsoftware.com> (raw)
Hello all,
Back in June I had done a test convert of our CVS repo using git 1.5.5.1
and cvs2svn 2.2.0 that went reasonably well (although it takes nearly a
week to finish!). Recently I wanted to try again with the latest
versions of git and cvs2svn.
When I get to the final stage (running git fast-import to build the
converted repo), I get the following output:
cat ../cvs2svn-tmp/git-blob.dat ../cvs2svn-tmp/git-dump.dat | git
fast-import
fatal: Unsupported command: '.
fast-import: dumping crash report to .git/fast_import_crash_19097
The crash is 18MB and I'd rather not post it, but the only bits that
seem somewhat interesting are:
fast-import crash report:
fast-import process: 19097
parent process : 19095
at Mon Jan 19 11:44:42 2009
fatal: Unsupported command: '.
Most Recent Commands Before Crash
---------------------------------
(...)
reset refs/tags/T_9772
from :1000007127
reset refs/heads/TAG.FIXUP
commit refs/heads/TAG.FIXUP
mark :1000007128
committer cvs2svn <cvs2svn> 1002043747 +0000
data 88
* '.
Has anyone got any ideas how to resolve this?
Thanks,
--
Kelly F. Hickel
Senior Product Architect
MQSoftware, Inc.
952-345-8677 Office
952-345-8721 Fax
kfh@mqsoftware.com
www.mqsoftware.com
Certified IBM SOA Specialty
Your Full Service Provider for IBM WebSphere Learn more at
www.mqsoftware.com
next reply other threads:[~2009-01-20 16:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 15:46 Kelly F. Hickel [this message]
2009-01-20 16:04 ` git fast-import problem converting from CVS with git 1.6.1 and cvs2svn 2.2.0 Kelly F. Hickel
2009-01-22 14:30 ` Kelly F. Hickel
2009-01-22 16:31 ` Johannes Schindelin
2009-01-23 4:14 ` Michael Haggerty
2009-01-20 16:41 ` Johannes Schindelin
2009-01-20 20:29 ` Daniel Barkalow
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=63BEA5E623E09F4D92233FB12A9F794302BC6851@emailmn.mqsoftware.com \
--to=kfh@mqsoftware.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).