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

Re: [RESEND PATCH 1/2] Fix builtin-fetch memory corruption by not overstepping array

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 14, 2007, 23:43 UTC
Message-ID
<7vr6l095kc.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20070914225953.GC16512@spearce.org>
"Shawn O. Pearce" <spearce@spearce.org> writes:
Show 5 quoted lines
>  *** RESEND TO CORRECT FROM+SBO ***
>
>  Sorry Junio.  I realized too late that the headers were wrong.
>  That's what I get for not configuring ~/.gitconfig on my amd64
>  Linux box.  ;-)

Actually this might have been a good thing, according to Linus. It is an evidence that you built and tested that change on the "blink" box not your usual box.

Previous: Shawn O. Pearce
Message 3 of 3 in “Fix builtin-fetch memory corruption by not overstepping array”
  1. 1/2 Fix builtin-fetch memory corruption by not overstepping arrayShawn O. Pearce, Sep 14, 2007
  2. Shawn O. PearceSep 14, 2007
  3. Junio C HamanoSep 14, 2007

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.