Re: Importing from CVS issues

From: Alex Bennee <kernel-hacker@bennee.com>
Date: Aug 16, 2005, 16:09 UTC
Message-ID: <1124208553.7444.47.camel@okra.transitives.com>
In-Reply-To: <46a038f90508160426450eff12@mail.gmail.com>

On Tue, 2005-08-16 at 23:26 +1200, Martin Langhoff wrote:

> I haven't seen this problem myself. There are some recent patches
> Junio merged that handle some oddities better. Give the 'pu' branch a
> go if you can.

I'll look at that in a bit. I already picked up a few of the patches mentioned on the list.

> I take it that the repo is not public. I'd like to try and reproduce
> the problem. Can you get it to happen with a public repository?

I'm afraid not. However I think I've found a problem when I tried running cvsps on its own to generate the patchset. It seems that REV_STR_MAX (cvsps-2.1/cvsps_types.h) wasn't big enough to contain some of our version strings.

This will be a feature of our development process which means all changes are based of branches, some of which branch multiple times and live for a long time before code is merged into the mainline. I don't know if any open source projects use CVS in such a way.

My import seems to be getting a lot further now. I now just need to clean out the corrupted files that are breaking cvs log.

-- Alex, homepage: http://www.bennee.com/~alex/ New systems generate new problems.