From: Michael Haggerty <mhagger@alum.mit.edu>
To: "Kelly F. Hickel" <kfh@mqsoftware.com>
Cc: git@vger.kernel.org, cvs2svn users <users@cvs2svn.tigris.org>
Subject: Re: git fast-import problem converting from CVS with git 1.6.1 and cvs2svn 2.2.0
Date: Fri, 23 Jan 2009 05:14:10 +0100 [thread overview]
Message-ID: <49794412.8070909@alum.mit.edu> (raw)
In-Reply-To: <63BEA5E623E09F4D92233FB12A9F794302BC6921@emailmn.mqsoftware.com>
Kelly F. Hickel wrote:
> 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.....
Yes, that would be helpful. Please include enough information and data
to enable me to reproduce your problem, because it is very mysterious.
The lines in question are (in Python)
self.f.write('data %d\n' % (len(log_msg),))
self.f.write('%s\n' % (log_msg,))
where self.f is a file that was opened in binary mode, and log_msg is an
8-bit or unicode string. Since the log message is being output to a
binary file, f.write() should squeal if the string includes any
non-ascii characters (I just verified this with Python 2.2, 2.4, and
2.5). Nevertheless, I suspect that your problem is caused by some kind
of character encoding problem, perhaps dependent on platform or Python
version.
You might also try the trunk version of cvs2svn; there have been a lot
of changes to cvs2git since release 2.1.1--even a new command that is
actually called cvs2git! (though for now you still need to use an
options file to start conversions).
Michael
------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=1044191
To unsubscribe from this discussion, e-mail: [users-unsubscribe@cvs2svn.tigris.org].
next prev parent reply other threads:[~2009-01-23 4:15 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
2009-01-22 16:31 ` Johannes Schindelin
2009-01-23 4:14 ` Michael Haggerty [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49794412.8070909@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=git@vger.kernel.org \
--cc=kfh@mqsoftware.com \
--cc=users@cvs2svn.tigris.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).