From: Shawn Pearce <spearce@spearce.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org, Dongsheng Song <dongsheng.song@gmail.com>
Subject: Re: git-repack: Outof memory
Date: Mon, 18 Sep 2006 02:50:55 -0400 [thread overview]
Message-ID: <20060918065055.GC20660@spearce.org> (raw)
In-Reply-To: <7v64flyjpe.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
> Shawn Pearce <spearce@spearce.org> writes:
>
> > ... I fear that
> > you are going to bump up against address space limitations soon
> > on 32 bit systems. Then you will bump up against the 4 GiB pack
> > file size limit. Which means you will need to use several packs
> > and avoid the '-a' flag when calling git-repack.
>
> I presume that you are hinting that we would need to update
> git-repack so that it is still useful without --all.
Yes. :-)
Apparently the Porcelain level is still open for debate. Someone
just needs to post a reasonable implementation to get discussion
(or lack there of) going. I'm too tired right now to try to roll
something up right, even though it looks to be rather simple.
As it is I'm having a difficult time navigating in vi to write this
email and normally vi navigation is as easy as breathing for me...
> I think pack-objects --unpacked=active-pack is ready, so I'll
> push it out.
Thanks; I noticed that in your "What's in git.git" announcement.
--
Shawn.
next prev parent reply other threads:[~2006-09-18 6:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-17 1:31 git-repack: Outof memory Dongsheng Song
2006-09-17 2:25 ` Shawn Pearce
[not found] ` <4b3406f0609161946x52a89dd3q6d74127c376270e7@mail.gmail.com>
[not found] ` <20060917031853.GC7512@spearce.org>
[not found] ` <4b3406f0609170003t63a2f9f4pf2c42faec9746a73@mail.gmail.com>
[not found] ` <4b3406f0609170543p68d96b9x9ba0c5a74d9e89e8@mail.gmail.com>
2006-09-18 0:23 ` Shawn Pearce
2006-09-18 2:47 ` Junio C Hamano
2006-09-18 6:50 ` Shawn Pearce [this message]
2006-09-17 21:09 ` Nicolas Pitre
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=20060918065055.GC20660@spearce.org \
--to=spearce@spearce.org \
--cc=dongsheng.song@gmail.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).