From: Jeff King <peff@peff.net>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: git@vger.kernel.org, Stefan Sperling <stsp@stsp.name>
Subject: Re: cvsimport: trying to convert freebsd cvs to git
Date: Sun, 23 Dec 2007 22:05:51 -0500 [thread overview]
Message-ID: <20071224030551.GA12495@sigill.intra.peff.net> (raw)
In-Reply-To: <20071222171801.GE15286@genesis.frugalware.org>
On Sat, Dec 22, 2007 at 06:18:01PM +0100, Miklos Vajna wrote:
> $ time git cvsimport -d `pwd`/cvs -C src.git src
> Initialized empty Git repository in /home/vmiklos/git/freebsd/src.git/.git/
> malformed revision
> fatal: refs/heads/origin: not a valid SHA1
> fatal: master: not a valid SHA1
> warning: You appear to be on a branch yet to be born.
> warning: Forcing checkout of HEAD.
> fatal: just how do you expect me to merge 0 trees?
> checkout failed: 256
I looked into this a bit more. The error is definitely coming from
cvsps. I can't even get a reasonable cvsps output for this repo
(presumably because of behind-the-scenes hackery on the RCS files).
E.g., try making a module with _just_
"src/release/Attic/MIRROR.SITES,v"; I can't even get a reasonable cvsps
output on that.
You might have better results with one of the other importers that have
been suggested, most of which are more robust in the face of CVS
oddities.
That being said, it's awful that git-cvsimport doesn't stop when cvsps
exits with an error, producing all of those meaningless errors. Patch
will follow.
-Peff
next prev parent reply other threads:[~2007-12-24 3:06 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
2007-12-23 17:29 ` Jeff King
2007-12-23 21:13 ` Martin Langhoff
2007-12-24 3:05 ` Jeff King [this message]
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=20071224030551.GA12495@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=stsp@stsp.name \
--cc=vmiklos@frugalware.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).