git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Troy Telford" <ttelford@linuxnetworx.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: git clone dies (large git repository)
Date: Mon, 21 Aug 2006 17:30:41 -0600	[thread overview]
Message-ID: <op.tenp9fv1ies9li@rygel.lnxi.com> (raw)
In-Reply-To: <7vfyfs313t.fsf@assigned-by-dhcp.cox.net>

On Sat, 19 Aug 2006 14:46:30 -0600, Junio C Hamano <junkio@cox.net> wrote:

> What is interesting is that .pack format does not have (as far
> as I know) inherent size limitation.  However, .idx file has
> hardcoded 32-bit offsets into .pack -- hence, in practice, you
> cannot use a .pack that is over 4GB locally.

Confessing my (complete, total, frightening) ignorance about git:  Is it  
even possible to take a large pack file and split it into smaller packs?

I'm thinking of it as an option for git-repack-- that the user can set the  
maximum size of any individual pack, and after that limit is reached, a  
new pack file is started.  (ie. --max-size 2GB) and will end up with two  
packs, each 2GB in size.

That being said -- I've been able to work around it (although I haven't  
tried your suggestion yet); it's not a 'critical' problem.  I'm now just  
curious if my fantasy (above) makes sense.
-- 
Troy Telford

  reply	other threads:[~2006-08-21 23:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-18 22:42 git clone dies (large git repository) Troy Telford
2006-08-19 10:58 ` Jakub Narebski
2006-08-19 20:46 ` Junio C Hamano
2006-08-21 23:30   ` Troy Telford [this message]
2006-08-22  0:23     ` Junio C Hamano
2006-08-22  0:42       ` Jakub Narebski

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=op.tenp9fv1ies9li@rygel.lnxi.com \
    --to=ttelford@linuxnetworx.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.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).