From: Jeff King <peff@peff.net>
To: Daniel Black <daniel.subs@internode.on.net>
Cc: git@vger.kernel.org
Subject: Re: cvsimport error when modulename is '.'
Date: Sun, 14 Feb 2010 02:07:58 -0500 [thread overview]
Message-ID: <20100214070757.GA22000@coredump.intra.peff.net> (raw)
In-Reply-To: <201002132251.42070.daniel.subs@internode.on.net>
On Sat, Feb 13, 2010 at 10:51:42PM +1100, Daniel Black wrote:
> git cvsimport -A ../authcvs-conv -k -m -v -d:pserver:anonymous@opendkim.cvs.sourceforge.net:/cvsroot/opendkim .
>
> this results in ...
>
> Initialized empty Git repository in /home/dan/software_projects/opendkim-import4/.git/
> Running cvsps...
> connect error: Network is unreachable
> cvs rlog: Logging .
> NOTICE: used alternate strip path /cvsroot/opendkim/.c
> WARNING: file /cvsroot/opendkim/BRANCHES doesn't match strip_path /cvsroot/opendkim/.c. ignoring
> WARNING: file /cvsroot/opendkim/FEATURES doesn't match strip_path /cvsroot/opendkim/.c. ignoring
These messages are not coming from git-cvsimport, but rather from cvsps,
which cvsimport uses to generate whole patchsets from the CVS data. Just
running "cvsps ." results in similar errors, and I don't see an obvious
way to do what you want. So probably it would require a patch to cvsps
to fix.
If this is a one-shot import, you can try a few different things.
As a hack, if you can move files in the CVS repository (and if you
can't, try using cvssuck or similar to pull them locally, and then do
the import from there), then move everything to a submodule "foo", and
import that module.
Alternatively, you might check out some of the alternative importers
like parsecvs or cvs2git. I don't know if they would handle this
situation better.
And as a super-hacky alternative, you could import each module
separately and then stich them all together using git-filter-branch.
-Peff
next prev parent reply other threads:[~2010-02-14 7:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-13 11:51 cvsimport error when modulename is '.' Daniel Black
2010-02-14 7:07 ` Jeff King [this message]
2010-02-16 11:21 ` Daniel Black
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=20100214070757.GA22000@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=daniel.subs@internode.on.net \
--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.
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).