git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "David Kågedal" <davidk@lysator.liu.se>
To: Andrew Myrick <amyrick@apple.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git-svn taking a long time
Date: Wed, 10 Feb 2010 23:25:11 +0100	[thread overview]
Message-ID: <873a18pw3c.fsf@krank.kagedal.org> (raw)
In-Reply-To: <87bpfxov6w.fsf@krank.kagedal.org> ("David Kågedal"'s message of "Wed, 10 Feb 2010 18:29:59 +0100")

David Kågedal <davidk@lysator.liu.se> writes:

> Andrew Myrick <amyrick@apple.com> writes:
>
>> Give 1.7.0-rc2 a try.  It includes commit 8bff7c5383ed833bd1df9c8d85c00a27af3e5b02, which attempts to persistently cache a lot of the processing that git-svn has to do on subversion's merge tickets, which has improved my fetch times significantly.  
>
> By "merge tickets", are you talking about the merge functionality that
> appeared in subversion 1.5? We don't use that.
>
> But I had another idea. I pecularity of our subversion repo is that we
> no longer use the foo/trunk branch, but only foo/branches/*. But we did
> once upon a time have a foo/trunk. And since I didn't include a "fetch =
> foo/trunk:refs/remotes/svn/trunk" in my config, it might need to refetch
> that information every time. For instance, the first revision is on
> trunk.
>
> I'm rerunning the fetch now with the trunk added, so see if it helps.

That seems to have done the trick. Now it's quick when there is nothing
to do.

Perhaps there is something in the git-svn caching that could still be
improved?

-- 
David Kågedal

      parent reply	other threads:[~2010-02-10 22:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-10 12:41 git-svn taking a long time David Kågedal
2010-02-10 16:59 ` Andrew Myrick
2010-02-10 17:29   ` David Kågedal
2010-02-10 17:39     ` Andrew Myrick
2010-02-10 22:25     ` David Kågedal [this message]

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=873a18pw3c.fsf@krank.kagedal.org \
    --to=davidk@lysator.liu.se \
    --cc=amyrick@apple.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).