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

Re: how to keep git-fetch from running out of memory?

From
Junio C Hamano <gitster@pobox.com>
Date
May 15, 2011, 20:25 UTC
Message-ID
<7vboz3pv7x.fsf@alter.siamese.dyndns.org>
In-Reply-To
<BANLkTinRkePRMQzQS7k=3bSTxTJRVpG39Q@mail.gmail.com>
Shawn Pearce <spearce@spearce.org> writes:
> However, that may still be insufficient. A big object must still be
> allocated in memory in order to compute its SHA-1.
I wonder if we can stream this?
Previous: Shawn PearceNext: Shawn Pearce
Message 3 of 4 in “how to keep git-fetch from running out of memory?”
  1. Kartik AgaramMay 15, 2011
  2. Shawn PearceMay 15, 2011
  3. Junio C HamanoMay 15, 2011
  4. Shawn PearceMay 15, 2011

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.