From: Pascal Obry <pascal@obry.net>
To: Eric Wong <normalperson@yhbt.net>
Cc: git list <git@vger.kernel.org>
Subject: Re: git-svn very slow on fetch (shared git-svn repo)
Date: Sun, 11 Oct 2009 11:00:15 +0200 [thread overview]
Message-ID: <4AD19E9F.8010302@obry.net> (raw)
In-Reply-To: <20091011070136.GB16264@dcvr.yhbt.net>
Hi Eric,
> For globs (branches and tags) the $GIT_DIR/svn/.metadata
> config file, under the svn-remote.svn.{branches,tags}-maxRev keys.
Right. I found out that copying the .metadata solve this problem.
> For explicitly specified refs (e.g. "trunk"), then it's in the last
> record of the corresponding rev_map (e.g.
> $GIT_DIR/svn/trunk/.rev_map.$UUID) as a 4-byte revision number + 20
> bytes of zeroes.
Seems like we do not need to copy this one as it is reconstructed by a
simple rebase on the trunk branch. This is quite fast as reconstructed
from the embedded git-svn-id if I'm not mistaken.
So you confirm that copying the .metadata is the solution?
Pascal.
--
--|------------------------------------------------------
--| Pascal Obry Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--| http://www.obry.net - http://v2p.fr.eu.org
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver keys.gnupg.net --recv-key F949BD3B
next prev parent reply other threads:[~2009-10-11 9:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-10 9:10 git-svn very slow on fetch (shared git-svn repo) Pascal Obry
2009-10-11 7:01 ` Eric Wong
2009-10-11 9:00 ` Pascal Obry [this message]
2009-10-11 9:03 ` Eric Wong
2009-10-11 9:37 ` Pascal Obry
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=4AD19E9F.8010302@obry.net \
--to=pascal@obry.net \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
/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).