From: Sean <seanlkml@sympatico.ca>
To: "Jon Smirl" <jonsmirl@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Using subversion tools on Mozilla CVS
Date: Sun, 4 Jun 2006 11:20:29 -0400 [thread overview]
Message-ID: <BAYC1-PASMTP08068F9BD23CF4FA8A1BDBAE970@CEZ.ICE> (raw)
Message-ID: <20060604112029.cb3405ab.seanlkml@sympatico.ca> (raw)
In-Reply-To: <9e4733910606032009p252ff5fai7401401427ae3ec3@mail.gmail.com>
On Sat, 3 Jun 2006 23:09:00 -0400
"Jon Smirl" <jonsmirl@gmail.com> wrote:
> I found this tool written in Python for importing CVS into Subversion.
> It seems to be handling the Mozilla CVS repository with fewer problems
> than parsecvs.
>
> http://cvs2svn.tigris.org/cvs2svn.html
>
> Since I'm not a native Python speaker, anyone else want to give a try
> at changing it to support git?
Hi Jon,
If you haven't tried to import into git with a recent version of
git-cvsimport, it would be worth a shot.
As for the tool you've referenced above, it does look pretty good.
It makes multiple passes and saves to a temp file after each, letting
you resume from that point and means it can use less memory overall.
It can produce a pretty straight forward looking dump file if you
pass it the "--dump-only" option, rather than it pushing the results
into svn; for instance:
$ cvs2svn --dump-only --dumpfile DUMPFILE <cvs directory>
It shouldn't be too hard to write a script that imports the revisions
found in the resulting DUMPFILE into git.
Sean
next prev parent reply other threads:[~2006-06-04 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-04 3:09 Using subversion tools on Mozilla CVS Jon Smirl
[not found] ` <20060604112029.cb3405ab.seanlkml@sympatico.ca>
2006-06-04 15:20 ` Sean [this message]
2006-06-04 15:48 ` Jon Smirl
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=BAYC1-PASMTP08068F9BD23CF4FA8A1BDBAE970@CEZ.ICE \
--to=seanlkml@sympatico.ca \
--cc=git@vger.kernel.org \
--cc=jonsmirl@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).