From: "Kelly F. Hickel" <kfh@mqsoftware.com>
To: "Kelly F. Hickel" <kfh@mqsoftware.com>, <git@vger.kernel.org>
Subject: RE: git fast-import problem converting from CVS with git 1.6.1 and cvs2svn 2.2.0
Date: Thu, 22 Jan 2009 08:30:39 -0600 [thread overview]
Message-ID: <63BEA5E623E09F4D92233FB12A9F794302BC6921@emailmn.mqsoftware.com> (raw)
In-Reply-To: <63BEA5E623E09F4D92233FB12A9F794302BC6855@emailmn.mqsoftware.com>
(Sorry for the mangled quotes)
> That is strange. The command "data 88" should read the next 88 bytes
and
> not stop at the line starting with '.
>
> Just to test, I successfully imported this:
>
> -- snip --
> commit refs/heads/testing/test
> mark :1
> committer cvs2svn <cvs2svn> 1002043747 +0000
> data 3
> '.
>
> -- snap --
>
> So I guess the problem lies much earlier: I could imagine that there
is
> _another_ "data" command that has a bogus length and just happens to
end
> after the line "data 88".
>
> Maybe that helps?
>
> I could also imagine that the '. actually is the end of an example
> inside a blob, that literally looks like a fast-import script, but
> actually is not meant for _this_ fast-import run.
>
> Ciao,
> Dscho
>
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@...
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> From: Daniel Barkalow
> Can you find that part of the input? I wouldn't be too surprised if
> something were giving the wrong length in a data command, causing it
to
> either eat another data command and end up in the data or to use
> not-quite-all of the data and end up near the end of the data.
>
> -Daniel
> *This .sig left intentionally blank*
>
>
I found the section in question, it is:
-- snip --
commit refs/heads/TAG.FIXUP
mark :1000007128
committer cvs2svn <cvs2svn> 1002043747 +0000
data 88
This commit was manufactured by cvs2svn to create tag
'T_BU_Problem_9xxx_Merge_3-21-2000'.
merge :1000007126
M 100755 :180810 mfcdev/Domedit/DlgAddAlias.h
-- snap --
By my count, 88 is the ending single quote character, leaving the '.' to
be interpreted as a command.
Looks like I should go post this on the cvs2svn list.....
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 prev parent reply other threads:[~2009-01-22 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 15:46 git fast-import problem converting from CVS with git 1.6.1 and cvs2svn 2.2.0 Kelly F. Hickel
2009-01-20 16:04 ` Kelly F. Hickel
2009-01-22 14:30 ` Kelly F. Hickel [this message]
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=63BEA5E623E09F4D92233FB12A9F794302BC6921@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).