From: "Jon Smirl" <jonsmirl@gmail.com>
To: git <git@vger.kernel.org>
Subject: Challenge: Importing Mozilla CVS into git
Date: Wed, 26 Jul 2006 17:08:18 -0400 [thread overview]
Message-ID: <9e4733910607261408m6f3980fbxc1793ca432ef3b0a@mail.gmail.com> (raw)
If anyone is looking for a project, it is still not possible to import
Mozilla CVS into git and then do increment updates. As I recall from
the last time I played with it, cvsps throws away some of the branches
because it thinks they are in a loop. parsecvs is unable to complete
the entire import without getting errors and aborting.
cvs2svn can import the entire Mozilla repository correctly. But it
imports it to svn and does not have incremental support.
Best solution would be to use the parser from parsecvs, apply the
change set detection algorithm from cvs2svn, and then add cvsps'
incremental update.
It's also not reasonable to fork git processes, there are about a
million change sets in Mozilla and it takes days of CPU time to do 1M
forks. The import app needs to use a library version of git. Another
tactic to reduce CPU time is to directly write pack files with the
delta in a first pass, and add the change set index in a later pass.
--
Jon Smirl
jonsmirl@gmail.com
reply other threads:[~2006-07-26 21:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9e4733910607261408m6f3980fbxc1793ca432ef3b0a@mail.gmail.com \
--to=jonsmirl@gmail.com \
--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).