From: "René Scharfe" <l.s.r@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2020, #04; Thu, 19)
Date: Sun, 22 Nov 2020 12:02:02 +0100 [thread overview]
Message-ID: <3b2afb7a-57aa-025c-806f-ae3faa0ed077@web.de> (raw)
In-Reply-To: <xmqqwnyeqpw9.fsf@gitster.c.googlers.com>
Am 21.11.20 um 23:57 schrieb Junio C Hamano:
> * 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é
next prev parent reply other threads:[~2020-11-22 11:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 22:57 What's cooking in git.git (Nov 2020, #04; Thu, 19) Junio C Hamano
2020-11-22 11:02 ` René Scharfe [this message]
2020-11-22 12:43 ` ag/merge-strategies-in-c [was Re: What's cooking in git.git (Nov 2020, #04; Thu, 19)] Alban Gruin
2020-11-23 19:15 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3b2afb7a-57aa-025c-806f-ae3faa0ed077@web.de \
--to=l.s.r@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).