git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brown <git@davidb.org>
To: Pascal Obry <pascal@obry.net>
Cc: Ollie Wild <aaw@google.com>, git@vger.kernel.org
Subject: Re: git-svn: .git/svn disk usage
Date: Sun, 2 Dec 2007 22:46:03 -0800	[thread overview]
Message-ID: <20071203064603.GA18583@old.davidb.org> (raw)
In-Reply-To: <4753A43F.9060303@obry.net>

On Mon, Dec 03, 2007 at 07:37:51AM +0100, Pascal Obry wrote:
>Ollie,
>
>> I'm curious if other developers have run into this issue.  If so, are
>> there any proposals / plans for improving the storage of git-svn
>> metadata?
>
>Did you run "git gc" after importing code form the subversion
>repository? On my side I found that it has reduced drastically the size
>of the local Git repository.

I think the original poster is probably finding the space in the .git/svn
directory.  'git-svn' keeps an index file for every branch in SVN.

I suspect it does this for speed, at least on a large import, since the SVN
commits will come across numerically, affecting the branches out of order.

However, the index could fairly easily be extracted from git (since that is
what it normally does).  In this case, where all of the indexes take
significant space if this is worth it.

Ollie, if you look in these svn branch directories, is most of the space
taken up with files called 'index'?

Browsing through the few svn clones that I have, the space seems to be
roughly split between 'index' files and 'unhandled.log' files.

Dave

  reply	other threads:[~2007-12-03  6:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-03  6:17 git-svn: .git/svn disk usage Ollie Wild
2007-12-03  6:37 ` Pascal Obry
2007-12-03  6:46   ` David Brown [this message]
2007-12-03  6:53     ` Kelvie Wong
2007-12-03 17:35     ` Ollie Wild
2007-12-04  8:29       ` Karl Hasselström
2007-12-03 18:51 ` David Voit
2007-12-05  8:54   ` Eric Wong
2007-12-05 21:30     ` Steven Grimm
2007-12-06  6:47       ` 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=20071203064603.GA18583@old.davidb.org \
    --to=git@davidb.org \
    --cc=aaw@google.com \
    --cc=git@vger.kernel.org \
    --cc=pascal@obry.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).