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

Re: What's cooking in git.git (Nov 2020, #04; Thu, 19)

From
René Scharfe <l.s.r@web.de>
Date
Nov 22, 2020, 11:02 UTC
Message-ID
<3b2afb7a-57aa-025c-806f-ae3faa0ed077@web.de>
In-Reply-To
<xmqqwnyeqpw9.fsf@gitster.c.googlers.com>
Am 21.11.20 um 23:57 schrieb Junio C Hamano:
Show 7 quoted lines
> * rs/chdir-notify-unleak (2020-11-16) 1 commit
>  - chdir-notify: UNLEAK registrated callback entries
>
>  Mark some stuff on list_head chain with UNLEAK() macro to squelch
>  leak checker.
>
>  Will merge to 'next'.

Please drop this one, it's too weak. We can get the same effect by reordering the struct members, but a better solution would be to actually free the allocations on exit.

René
Previous: Junio C HamanoNext: Alban Gruin
Message 2 of 4 in “What's cooking in git.git (Nov 2020, #04; Thu, 19)”
  1. Junio C HamanoNov 21, 2020
  2. René ScharfeNov 22, 2020
  3. ag/merge-strategies-in-c [was Re: What's cooking in git.git (Nov 2020, #04; Thu, 19)]Alban Gruin, Nov 22, 2020
  4. Junio C HamanoNov 23, 2020

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.