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

Re: [PATCH 0/2] [RFT] git-svn: more efficient revision -> commit mapping

From
HHHarvey Harrison <harvey.harrison@gmail.com>
Date
Dec 10, 2007, 01:04 UTC
Message-ID
<1197248646.7185.25.camel@brick>
In-Reply-To
<1197233768.7185.6.camel@brick>
On Sun, 2007-12-09 at 12:56 -0800, Harvey Harrison wrote:
Show 21 quoted lines
> On Sat, 2007-12-08 at 23:27 -0800, Eric Wong wrote:
> > This is very lightly tested, but describes the format I described in:
> > 
> >   http://article.gmane.org/gmane.comp.version-control.git/67126
> > 
> >   (more in the commit messages)
> > 
> > I'll be out of town the next few days and I'm not sure how much I'll be
> > able to follow up on it while I'm gone.  Please test, especially if
> > you're dealing with a repository where large .rev_db files are a
> > problem.
> > 
> > Junio: not intended for master just yet, but if you hear nothing but
> > good things about it, feel free :)
> Preliminary tests against the gcc repo are going swimmingly.
> 
> Successful git svn rebase against trunk, doing a full git svn fetch
> now to build rev_maps for all svn branches/tags.  At halfway through
> space has decreased from ~2GB to 17MB for about half of the needed
> metadata.
> 
Eric,

I'm very happy with these patches. For the gcc repo, git-svn metadata has gone from over 5GB to 33MB. git-svn fetch/rebase are working fine, will shout if I see any odd behavior.

Harvey
Previous: Harvey HarrisonNext: Eric Wong
Message 5 of 8 in “[RFT] git-svn: more efficient revision -> commit mapping”
  1. 0/2 [RFT] git-svn: more efficient revision -> commit mappingEric Wong, Dec 9, 2007
  2. 1/2 git-svn: replace .rev_db with a more space-efficient .rev_map formatEric Wong, Dec 9, 2007
  3. 2/2 git-svn: reinstate old rev_db optimization in new rev_mapEric Wong, Dec 9, 2007
  4. Harvey HarrisonDec 9, 2007
  5. Harvey HarrisonDec 10, 2007
  6. Eric WongDec 12, 2007
  7. Sam VilainDec 13, 2007
  8. Eric WongDec 13, 2007

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.