From: Nick Woolley <nickwoolley@yahoo.co.uk>
To: Alex Bennee <kernel-hacker@bennee.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC] git-cvs script
Date: Mon, 01 Jun 2009 10:47:52 +0100 [thread overview]
Message-ID: <4A23A3C8.3090506@yahoo.co.uk> (raw)
In-Reply-To: <b2cdc9f30905310042u592a6f5cv541055194524cce0@mail.gmail.com>
Alex Bennee wrote:
> If this is using the inbuilt cvsps and perl then it will likely choke
> on very large CVS repos. For some CVS tree's I've had to resort to a
> hacked up version of parsecvs to get a conversion running.
I gather cvsps has to read the whole history to be able to interpret the latest
commits, is that right? In which case a long history is going to generate long
waits on each import. And possibly eat lots of memory too.
I do actually have a larger CVS tree to test it on than I have been using (it's
about a decade's worth of changes on a production website) but I didn't want to
set myself up for a fall by tackling it. For now, my aim has been to keep CVS
"out of the living room" whilst I work on the small CVS module that concerns me.
Meanwhile, I'm hoping to convince the powers that be that CVS needs to be
replaced, preferably with Git, before I get asked to work on something larger.
However, if you can test it on your repository, and with your patched version of
parsecvs, that would be a good thing. Especially if it works.
Thanks,
N
prev parent reply other threads:[~2009-06-01 9:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-30 13:41 [RFC] git-cvs script Nick Woolley
2009-05-30 23:33 ` Junio C Hamano
2009-06-01 10:47 ` Nick Woolley
2009-05-31 7:42 ` Alex Bennee
2009-06-01 9:47 ` Nick Woolley [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A23A3C8.3090506@yahoo.co.uk \
--to=nickwoolley@yahoo.co.uk \
--cc=git@vger.kernel.org \
--cc=kernel-hacker@bennee.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).