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

Re: git-fetch fails with error code 128

From
Junio C Hamano <junkio@cox.net>
Date
Dec 16, 2006, 00:37 UTC
Message-ID
<7vy7p8llql.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<Pine.LNX.4.64.0612151706150.18171@xanadu.home>
Nicolas Pitre <nico@cam.org> writes:
Show 8 quoted lines
> I really doubt it is a compatibility problem.  The provided error 
> message may only result from the fact that patch_delta() has returned 
> NULL.
>
> And since patch-delta is really simple, it doesn't have many reasons for 
> returning NULL: either the object store on either the remote or local 
> side is corrupted in which case a git-fsck-objects --full should catch 
> that, or the system ran out of memory.

Hmmmm. True and sad. Sad because I do not offhand think of places to trim the memory usage.

Previous: Nicolas PitreNext: Andy Parkins
Message 7 of 10 in “git-fetch fails with error code 128”
  1. Andy ParkinsDec 14, 2006
  2. Shawn PearceDec 14, 2006
  3. Junio C HamanoDec 15, 2006
  4. Andy ParkinsDec 15, 2006
  5. Junio C HamanoDec 15, 2006
  6. Nicolas PitreDec 15, 2006
  7. Junio C HamanoDec 16, 2006
  8. Andy ParkinsDec 16, 2006
  9. Andy ParkinsDec 16, 2006
  10. Nicolas PitreDec 15, 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.