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

Re: [PATCH 0/4] Memory leak fixes

From
Jeff King <peff@peff.net>
Date
Nov 6, 2023, 17:32 UTC
Message-ID
<20231106173205.GD10414@coredump.intra.peff.net>
In-Reply-To
<cover.1699267422.git.ps@pks.im>
On Mon, Nov 06, 2023 at 11:45:48AM +0100, Patrick Steinhardt wrote:
> this patch series fixes some memory leaks. All of these leaks have been
> found while working on the reftable backend.

All four look good to me (and the refactoring in 3/4 is very cleanly done).

-Peff
Previous: Patrick SteinhardtNext: Junio C Hamano
Message 8 of 9 in “Memory leak fixes”
  1. 0/4 Memory leak fixesPatrick Steinhardt, Nov 6, 2023
  2. 1/4 test-bloom: stop setting up Git directory twicePatrick Steinhardt, Nov 6, 2023
  3. Jeff KingNov 6, 2023
  4. 2/4 shallow: fix memory leak when registering shallow rootsPatrick Steinhardt, Nov 6, 2023
  5. Jeff KingNov 6, 2023
  6. 3/4 setup: refactor `upgrade_repository_format()` to have common exitPatrick Steinhardt, Nov 6, 2023
  7. 4/4 setup: fix leaking repository formatPatrick Steinhardt, Nov 6, 2023
  8. Jeff KingNov 6, 2023
  9. Junio C HamanoNov 7, 2023

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.