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

Re: git-svn mergeinfo support performance problem

From
Johan 't Hart <johanthart@gmail.com>
Date
Dec 20, 2009, 00:28 UTC
Message-ID
<4B2D6FB0.6080103@gmail.com>
In-Reply-To
<6b2f9b1d0912181708g32645b48j3886b74101e77d80@mail.gmail.com>
Andrew Myrick schreef:
Show 6 quoted lines
> I've been testing git-svn v1.6.6-rc3's mergeinfo support on a large
> svn repository (60,000+ revisions, 20+ GiB) that uses a very
> branch-heavy integration model in which every change gets its own
> branch before being committed to trunk.  As a result of the model,
> there are currently over 1000 lines in the svn:mergeinfo property on
> trunk.
Just wondering: Isnt this workflow stalling svn itself alot too?

And also: Do you delete the branches after you reintegrated them? If so, I think its safe for you to cleanup the svn mergeinfo once in a while. That should not affect 'svn log -g' because the mergeinfo is still there in older revisions. I think svn benefits from this too...

Previous: Andrew MyrickNext: Andrew Myrick
Message 2 of 3 in “git-svn mergeinfo support performance problem”
  1. Andrew MyrickDec 19, 2009
  2. Johan 't HartDec 20, 2009
  3. Andrew MyrickDec 20, 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.