From: Junio C Hamano <junkio@cox.net>
To: Shawn Pearce <spearce@spearce.org>
Cc: git@vger.kernel.org, Dongsheng Song <dongsheng.song@gmail.com>
Subject: Re: git-repack: Outof memory
Date: Sun, 17 Sep 2006 19:47:25 -0700 [thread overview]
Message-ID: <7v64flyjpe.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 20060918002357.GA19727@spearce.org
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.
Which means "pack-objects --unpacked=active-pack" would need to
be pushed out so that git-repack can be updated to do the
"archived ones and repacking the active pack" we talked about
earlier.
I think pack-objects --unpacked=active-pack is ready, so I'll
push it out.
next prev parent reply other threads:[~2006-09-18 2:47 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 [this message]
2006-09-18 6:50 ` Shawn Pearce
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=7v64flyjpe.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=dongsheng.song@gmail.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.