git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: "Karl Hasselström" <kha@treskal.com>
Cc: git@vger.kernel.org
Subject: Re: speeding up git-svn when directories are copied?
Date: Mon, 23 Apr 2007 18:54:05 -0700	[thread overview]
Message-ID: <20070424015405.GA7232@untitled> (raw)
In-Reply-To: <20070423141601.GA5797@diana.vm.bytemark.co.uk>

Karl Hasselström <kha@treskal.com> wrote:
> When importing a whole repository, git-svn currently takes a _lot_ of
> time. Almost all of it seems to be spent getting the full text of each
> and every file when a tag or new branch is created.

Try SVN 1.4.3 with my patch[1] to get do_switch() working.
trunk should work without the patch.

[1] - http://svn.haxx.se/dev/archive-2007-01/0936.shtml

do_switch() is broken otherwise, and do_update() is extremely
inefficient.

-- 
Eric Wong

  reply	other threads:[~2007-04-24  1:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-23 14:16 speeding up git-svn when directories are copied? Karl Hasselström
2007-04-24  1:54 ` Eric Wong [this message]
2007-04-24 10:01   ` Karl Hasselström
2007-04-26 15:45     ` Eric Wong

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=20070424015405.GA7232@untitled \
    --to=normalperson@yhbt.net \
    --cc=git@vger.kernel.org \
    --cc=kha@treskal.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).