All of lore.kernel.org
 help / color / mirror / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] github-ci: update macos jobs to macos-15
Date: Sat, 17 Oct 2026 13:36:25 +0000	[thread overview]
Message-ID: <atN52HNEzdSeh19l@fruit.crustytoothpaste.net> (raw)
In-Reply-To: <xmqqfqy5clgz.fsf@gitster.g>

[-- Attachment #1: Type: text/plain, Size: 909 bytes --]

On 2026-10-16 at 22:46:36, Junio C Hamano wrote:
> GitHub from <no-reply@github.com> address keeps sending
> 
>   Subject: [Action Required] macOS 14 hosted runner image is closing down
> 
> and suggests to update to either macos-latest (macos-26) or
> macos-15.  As we do not have strong reason to pick one over the
> other, this patch picks more conservative choice with hopefully
> smaller impact.
> 
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
> ---
>  * Not tested at all and I do not do macos myself.

I think this is fine if it passes CI.  There's not that much of a
difference in terms of POSIX-related functionality in different versions
of macOS, so upgrading to macOS 15 shouldn't be a problem.  I think 15
is a better option than 26 because we're more likely to avoid anything
new that older versions don't have.
-- 
brian m. carlson (they/them)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 325 bytes --]

      reply	other threads:[~2026-10-17 13:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16 22:46 [PATCH] github-ci: update macos jobs to macos-15 Junio C Hamano
2026-10-17 13:36 ` brian m. carlson [this message]

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=atN52HNEzdSeh19l@fruit.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --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 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.