From: Sam Vilain <sam@vilain.net>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: Lachlan Deck <lachlan.deck@gmail.com>, git@vger.kernel.org
Subject: Re: git-svn init/fetch: wow that's slow
Date: Wed, 22 Apr 2009 23:05:52 +1200 [thread overview]
Message-ID: <1240398352.20236.26.camel@maia.lan> (raw)
In-Reply-To: <fabb9a1e0904220255w55c8fee1uf534aad07cefa818@mail.gmail.com>
On Wed, 2009-04-22 at 11:55 +0200, Sverre Rabbelier wrote:
> Heya,
>
> On Wed, Apr 22, 2009 at 09:40, Lachlan Deck <lachlan.deck@gmail.com> wrote:
> > Okay, so I'm using git 1.6.2. I assume this is all a 'known issue'. Has
> > there been any work / plans towards improving this?
>
> This can be improved by using svn 1.5's delta feature, however, Eric
> (the author of git-svn) does not have the time to do this, and no-one
> has stepped up to do this.
> A workaround is to not clone from r1 but instead start at a more
> recent revision.
Fetching over plain svn:// is IME much faster. But let's face it, SVN
is no race-horse and was never designed for the case where people like
to look at their history much. Developing with a trunk was so painful,
people would rather just forget...
One workaround is to use SVK to do the initial mirroring, and the
--use-svm-mirror flag to convert your SVK mirror path to git. See
http://utsl.gen.nz/talks/git-svn/intro.html for a guide for the second
part of that. SVK has implemented some of the harder parts of the SVN
API to get right, such as request pipelining - see
http://code.bestpractical.com/svk/trunk/lib/SVK/Mirror/Backend/SVNRaPipe.pm for how the SVN API "supports" this. As a result of this dedication to the cause, SVK does this part very quickly.
Sam
next prev parent reply other threads:[~2009-04-22 11:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 7:40 git-svn init/fetch: wow that's slow Lachlan Deck
2009-04-22 9:55 ` Sverre Rabbelier
2009-04-22 11:05 ` Sam Vilain [this message]
2009-04-22 11:16 ` Matthieu Moy
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=1240398352.20236.26.camel@maia.lan \
--to=sam@vilain.net \
--cc=git@vger.kernel.org \
--cc=lachlan.deck@gmail.com \
--cc=srabbelier@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.