From: Harvey Harrison <harvey.harrison@gmail.com>
To: Eric Wong <normalperson@yhbt.net>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH 0/2] [RFT] git-svn: more efficient revision -> commit mapping
Date: Sun, 09 Dec 2007 12:56:08 -0800 [thread overview]
Message-ID: <1197233768.7185.6.camel@brick> (raw)
In-Reply-To: <1197185262-16765-1-git-send-email-normalperson@yhbt.net>
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.
Cheers,
Harvey
next prev parent reply other threads:[~2007-12-09 20:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-09 7:27 [PATCH 0/2] [RFT] git-svn: more efficient revision -> commit mapping Eric Wong
2007-12-09 7:27 ` [PATCH 1/2] git-svn: replace .rev_db with a more space-efficient .rev_map format Eric Wong
2007-12-09 7:27 ` [PATCH 2/2] git-svn: reinstate old rev_db optimization in new rev_map Eric Wong
2007-12-09 20:56 ` Harvey Harrison [this message]
2007-12-10 1:04 ` [PATCH 0/2] [RFT] git-svn: more efficient revision -> commit mapping Harvey Harrison
2007-12-12 18:05 ` Eric Wong
2007-12-13 2:42 ` Sam Vilain
2007-12-13 16:30 ` Eric Wong
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=1197233768.7185.6.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).