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

Re: [PATCH] unpack-trees: plug a memory leak

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 13, 2013, 21:50 UTC
Message-ID
<7v1u5xw99t.fsf@alter.siamese.dyndns.org>
In-Reply-To
<520AA5FE.1090208@web.de>
René Scharfe <l.s.r@web.de> writes:
Show 8 quoted lines
>> It was lost in the follow-up discussion and I missed it.
>
> I had forgotten about it as well, until Felipe mentioned it again.
>
>> I assume that this is signed-off by you as a forwarder?  I'd prefer
>> to even mark it Reviewed-by: you.
>
> Right, I did review the patch and you can tag it as such.
OK, will queue and soon merge to and cook in 'next'.
Thanks, everybody.
Previous: René ScharfeNext: Felipe Contreras
Message 8 of 9 in “Huge possible memory leak while cherry-picking.”
  1. Лежанкин ИванAug 9, 2013
  2. Felipe ContrerasAug 9, 2013
  3. Лежанкин ИванAug 12, 2013
  4. Felipe ContrerasAug 12, 2013
  5. unpack-trees: plug a memory leakRené Scharfe, Aug 13, 2013
  6. Junio C HamanoAug 13, 2013
  7. René ScharfeAug 13, 2013
  8. Junio C HamanoAug 13, 2013
  9. Felipe ContrerasAug 12, 2013

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.