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

[RFC] leaky()

From
Pierre Habouzit <madcoder@debian.org>
Date
Jun 24, 2008, 20:14 UTC
Message-ID
<1214338474-16822-1-git-send-email-madcoder@debian.org>

In the parse-options thread, it appears that we may somethings leak some tiny bits of memory on purpose. So that it makes life of people searching for real memory leaks easier.

The second patch marks the leaks I'm responsible for in git (and that I'm aware of) as leaky().

Next: Pierre Habouzit
Message 1 of 9 in “[RFC] leaky()”
  1. Pierre HabouzitJun 24, 2008
  2. 1/2 Introduce leaky().Pierre Habouzit, Jun 24, 2008
  3. 2/2 git-rev-parse: use leaky().Pierre Habouzit, Jun 24, 2008
  4. Pierre HabouzitJun 24, 2008
  5. Jakub NarebskiJun 24, 2008
  6. Pierre HabouzitJun 24, 2008
  7. Junio C HamanoJun 26, 2008
  8. Pierre HabouzitJun 26, 2008
  9. Jan HudecJul 22, 2008

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.