From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: git clone dies (large git repository)
Date: Tue, 22 Aug 2006 02:42:53 +0200 [thread overview]
Message-ID: <ecdjub$bed$1@sea.gmane.org> (raw)
In-Reply-To: 7v3bbpty7j.fsf@assigned-by-dhcp.cox.net
Junio C Hamano wrote:
> "Troy Telford" <ttelford@linuxnetworx.com> writes:
>
>> 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.
>
> The way I would suggest you do it is not by size but by distance
> from the latest. If you want to split the kernel history for
> example, you repack up to 2.6.14 for example, and then repack
> the remainder. That way, you can optimize for size for older
> (presumably less frequently used) data while optimizing for
> speed for more reent stuff.
If there would be some enhancement to pack files allowing either limiting
the size of pack (e.g. filesystem limits, mmap limits) and/or mmaping only
fragment or fragments of pack file, the maximal size of the pack, or
maximal size of the mmapped fragment should be configurable per repository,
not olny as an option to some command (git-repack for example).
Probably would need some enhancement to git-fetch/git-clone too...
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
prev parent reply other threads:[~2006-08-22 0:43 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
2006-08-22 0:23 ` Junio C Hamano
2006-08-22 0:42 ` Jakub Narebski [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ecdjub$bed$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).