git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git-repack: Outof memory

From
Junio C Hamano <junkio@cox.net>
Date
Sep 18, 2006, 02:47 UTC
Message-ID
<7v64flyjpe.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20060918002357.GA19727@spearce.org>
Shawn Pearce <spearce@spearce.org> writes:
Show 5 quoted lines
> ...  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.

Previous: Shawn PearceNext: Shawn Pearce
Message 5 of 6 in “git-repack: Outof memory”
  1. Dongsheng SongSep 17, 2006
  2. Shawn PearceSep 17, 2006
  3. Nicolas PitreSep 17, 2006
  4. Shawn PearceSep 18, 2006
  5. Junio C HamanoSep 18, 2006
  6. Shawn PearceSep 18, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.