From: Alex Bennee <kernel-hacker@bennee.com>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Importing from CVS issues
Date: Tue, 16 Aug 2005 17:09:13 +0100 [thread overview]
Message-ID: <1124208553.7444.47.camel@okra.transitives.com> (raw)
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.
next prev parent reply other threads:[~2005-08-16 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 10:41 Importing from CVS issues Alex Bennee
2005-08-16 11:26 ` Martin Langhoff
2005-08-16 16:09 ` Alex Bennee [this message]
2005-08-16 12:16 ` David Kågedal
2005-08-16 13:48 ` Alex Bennee
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=1124208553.7444.47.camel@okra.transitives.com \
--to=kernel-hacker@bennee.com \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.com \
/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).