From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2022, #06; Wed, 19)
Date: Thu, 20 Oct 2022 08:38:32 -0700 [thread overview]
Message-ID: <xmqqmt9qmrnr.fsf@gitster.g> (raw)
In-Reply-To: <Y1DoHb1vRYpIyPzK@coredump.intra.peff.net> (Jeff King's message of "Thu, 20 Oct 2022 02:18:05 -0400")
Jeff King <peff@peff.net> writes:
> On Wed, Oct 19, 2022 at 06:31:16PM -0700, Junio C Hamano wrote:
>
>> * jk/use-o0-in-leak-sanitizer (2022-10-19) 1 commit
>> (merged to 'next' on 2022-10-19 at 27c2546b98)
>> + Makefile: force -O0 when compiling with SANITIZE=leak
>>
>> Avoid false-positive from LSan whose assumption may be broken with
>> higher optimization levels.
>>
>> Will merge to 'master'.
>> source: <Y08JZVDgJpJvrBiz@coredump.intra.peff.net>
>
> BTW, you should be able to see that "next" now passes the leaks CI job
> (because of this patch), but master doesn't yet.
Yup, thanks!
Unfortunately, without some CI/make updates, we cannot verify that
macOS builds are green again without Apple Crypto X-<.
next prev parent reply other threads:[~2022-10-20 15:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 1:31 What's cooking in git.git (Oct 2022, #06; Wed, 19) Junio C Hamano
2022-10-20 6:18 ` Jeff King
2022-10-20 15:38 ` Junio C Hamano [this message]
2022-10-20 9:56 ` pw/rebase-reflog-fixes (was Re: What's cooking in git.git (Oct 2022, #06; Wed, 19)) Phillip Wood
2022-10-21 1:16 ` What's cooking in git.git (Oct 2022, #06; Wed, 19) Michael McClimon
2022-10-21 4:55 ` Jeff King
2022-10-21 19:45 ` Glen Choo
2022-10-22 22:11 ` Jeff King
2022-10-21 3:15 ` tb/remove-unused-pack-bitmap Taylor Blau
-- strict thread matches above, loose matches on Subject: below --
2022-10-20 1:34 What's cooking in git.git (Oct 2022, #06; Wed, 19) Junio C Hamano
2022-10-20 11:57 ` Philip Oakley
2022-10-20 15:35 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqmt9qmrnr.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).