Re: cvsimport error when modulename is '.'

From: Daniel Black <daniel.subs@internode.on.net>
Date: Feb 16, 2010, 11:21 UTC
Message-ID: <201002162221.58483.daniel.subs@internode.on.net>
In-Reply-To: <20100214070757.GA22000@coredump.intra.peff.net>

On Sunday 14 February 2010 18:07:58 Jeff King wrote:

> On Sat, Feb 13, 2010 at 10:51:42PM +1100, Daniel Black wrote:

> These messages are not coming from git-cvsimport, but rather from cvsps,

thanks for narrowing it down. I'll see if I can track down the maintainer there.

> 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.

thanks for confirming this.

> If this is a one-shot import, you can try a few different things.

was hoping not too but i might be able to get the project team on board with a 
one-shot.

> As a hack, if you can move files in the CVS repository

on sf its easy as you've got read rsync access on the source

> (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.

might to this .

> 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.

ok

> And as a super-hacky alternative, you could import each module
> separately and then stich them all together using git-filter-branch.

Yep was thinking of this. Thanks for the expert advice on the stiching together because i had no idea how.

Much appreciate your time for putting together these options.

Thanks Jeff.