From: Patrick Steinhardt <ps@pks.im>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, "René Scharfe" <l.s.r@web.de>,
"Junio C Hamano" <gitster@pobox.com>
Subject: Re: [PATCH 3/5] thread-utils: introduce optional barrier type
Date: Fri, 3 Jan 2025 07:45:47 +0100 [thread overview]
Message-ID: <Z3eHm-X39LcE8vMy@pks.im> (raw)
In-Reply-To: <20250101182826.GB1391912@coredump.intra.peff.net>
On Wed, Jan 01, 2025 at 01:28:26PM -0500, Jeff King wrote:
> On Mon, Dec 30, 2024 at 08:03:38AM +0100, Patrick Steinhardt wrote:
> > Okay. The Meson equivalent would be:
> > [...]
>
> Yeah, I figured it would need something similar (but for our CI it does
> not yet matter). Do you want to prepare that as a patch on top? (Though
> also see the message I'm about to send that we might be able to avoid
> this series entirely!).
Looks like your version was reverted in favor of the new version you
have sent. So I'll refrain from doing that :)
Patrick
next prev parent reply other threads:[~2025-01-03 6:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-30 4:23 [PATCH 0/5] fixing thread races in linux-leaks CI Jeff King
2024-12-30 4:24 ` [PATCH 1/5] test-lib: use individual lsan dir for --stress runs Jeff King
2024-12-30 4:34 ` Jeff King
2024-12-30 17:08 ` Junio C Hamano
2024-12-30 4:26 ` [PATCH 2/5] Revert "index-pack: spawn threads atomically" Jeff King
2024-12-30 4:28 ` [PATCH 3/5] thread-utils: introduce optional barrier type Jeff King
2024-12-30 7:03 ` Patrick Steinhardt
2025-01-01 18:28 ` Jeff King
2025-01-03 6:45 ` Patrick Steinhardt [this message]
2024-12-30 4:29 ` [PATCH 4/5] index-pack: work around LSan threading race with barrier Jeff King
2024-12-30 4:30 ` [PATCH 5/5] grep: " Jeff King
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=Z3eHm-X39LcE8vMy@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=l.s.r@web.de \
--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.
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).