From: Jacob Helwig <jacob.helwig@gmail.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: git@vger.kernel.org
Subject: Re: Speed of conversion from Subversion repository to Git
Date: Mon, 1 Feb 2010 10:17:07 -0800 [thread overview]
Message-ID: <8c9a061002011017l6127dd22na1930481c7b59d4@mail.gmail.com> (raw)
In-Reply-To: <4B6717DF.8020004@web.de>
On Mon, Feb 1, 2010 at 10:05, Markus Elfring <Markus.Elfring@web.de> wrote:
> Hello,
>
> I am trying to convert the YaST Subversion repository into a Git variant on my
> system. Unfortunately, a command like "svn2git
> http://svn.opensuse.org/svn/yast/" does not finish this attempt after 1,5 days
> (> 715:13.24 CPU time) here. I would appreciate suggestions for improvements of
> the execution speed.
> (Renicing of the process "git-svn" does not help to increase its processor
> utilisation in noticeable ways.)
>
> Regards,
> Markus
>
We're in the process of converting to Git at work, and I've found that
svn-all-fast-export was the best option for us. git-svn's behavior of
a branch's entire history every time it found a new branch (even
though it has already seen 3/4 of the revisions involved) caused it to
be far too slow for our needs. Admittedly, this was ~1 year ago that
I tried git-svn to do a test conversion, and things might have
improved since then.
svn-all-fast-export does require access to the raw repository, instead
of just (http|svn|svn+ssh):// access, but it does allow you to split
out one SVN "repository" into multiple Git repositories in one go.
-Jacob
next prev parent reply other threads:[~2010-02-01 18:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 18:05 Speed of conversion from Subversion repository to Git Markus Elfring
2010-02-01 18:17 ` Jacob Helwig [this message]
2010-02-02 11:20 ` Markus Elfring
2010-02-11 17:10 ` Markus Elfring
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=8c9a061002011017l6127dd22na1930481c7b59d4@mail.gmail.com \
--to=jacob.helwig@gmail.com \
--cc=Markus.Elfring@web.de \
--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).