From: Junio C Hamano <gitster@pobox.com>
To: "René Scharfe" <l.s.r@web.de>
Cc: git@vger.kernel.org, Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: What's cooking in git.git (Mar 2026, #08)
Date: Sun, 22 Mar 2026 10:50:07 -0700 [thread overview]
Message-ID: <xmqqwlz392k0.fsf@gitster.g> (raw)
In-Reply-To: <6c108696-2d41-4fa1-9662-fbf6db97f767@web.de> ("René Scharfe"'s message of "Sun, 22 Mar 2026 17:30:44 +0100")
René Scharfe <l.s.r@web.de> writes:
> On 3/22/26 7:46 AM, Junio C Hamano wrote:
>> * js/macos-homebrew-forgets-reg-enhanced (2026-03-20) 1 commit
>> - osx-clang: work around Homebrew's clang lacking REG_ENHANCED
>>
>> The build on macOS with Clang is fixed to work around a Homebrew change
>> that exposed an issue with missing REG_ENHANCED.
>>
>> Will merge to 'next'?
>> source: <d340af9e-334c-4e81-e58a-fc3dea73ebdd@gmx.de>
> This seems to no longer be necessary -- the latest workflow run on
> master succeeded (https://github.com/git/git/actions/runs/23392330338).
Yeah, I saw that too and was wondering if the glitch was reverted or
something at the platform side.
> Did some kind soul fix the runners?
If so, thanks. It certainly was not me ;-)
next prev parent reply other threads:[~2026-03-22 17:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-22 6:46 What's cooking in git.git (Mar 2026, #08) Junio C Hamano
2026-03-22 14:14 ` Shreyansh Paliwal
2026-03-22 17:53 ` Junio C Hamano
2026-03-22 16:30 ` René Scharfe
2026-03-22 17:50 ` Junio C Hamano [this message]
2026-03-23 16:32 ` Johannes Schindelin
2026-03-23 16:54 ` Junio C Hamano
2026-03-22 20:49 ` 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=xmqqwlz392k0.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--cc=l.s.r@web.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.