From: Andrew Myrick <amyrick@apple.com>
To: "David Kågedal" <davidk@lysator.liu.se>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git-svn taking a long time
Date: Wed, 10 Feb 2010 09:39:15 -0800 [thread overview]
Message-ID: <E8C897D9-F8EB-4FF3-B27C-9679E008795A@apple.com> (raw)
In-Reply-To: <87bpfxov6w.fsf@krank.kagedal.org>
On Feb 10, 2010, at 9:29 AM, David Kågedal wrote:
> 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.
I do mean that. If you don't use them, then I'm stumped.
> 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.
>
> And another note is that "git svn fetch --parent" was always quick.
Sounds reasonable. Good luck!
-Andrew
next prev parent reply other threads:[~2010-02-10 17:39 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 [this message]
2010-02-10 22:25 ` David Kågedal
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=E8C897D9-F8EB-4FF3-B27C-9679E008795A@apple.com \
--to=amyrick@apple.com \
--cc=davidk@lysator.liu.se \
--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).