git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git-svn very slow on fetch (shared git-svn repo)

From
EWEric Wong <normalperson@yhbt.net>
Date
Oct 11, 2009, 09:03 UTC
Message-ID
<20091011090338.GA27480@dcvr.yhbt.net>
In-Reply-To
<4AD19E9F.8010302@obry.net>
Pascal Obry <pascal@obry.net> wrote:
Show 17 quoted lines
> 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?

Yes, copying .metadata should be enough. The .rev_map rebuild should be fast.

-- 
Eric Wong
Previous: Pascal ObryNext: Pascal Obry
Message 4 of 5 in “git-svn very slow on fetch (shared git-svn repo)”
  1. Pascal ObryOct 10, 2009
  2. Eric WongOct 11, 2009
  3. Pascal ObryOct 11, 2009
  4. Eric WongOct 11, 2009
  5. Pascal ObryOct 11, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.