From: Junio C Hamano <gitster@pobox.com>
To: Todd Zullinger <tmz@pobox.com>
Cc: git@vger.kernel.org, Patrick Steinhardt <ps@pks.im>
Subject: Re: [PATCH v2] github-ci: update macos jobs to macos-15
Date: Mon, 19 Oct 2026 18:14:39 -0700 [thread overview]
Message-ID: <xmqqpkx5yxz4.fsf@gitster.g> (raw)
In-Reply-To: <20261019234724.H0mV3jqQ@teonanacatl.net> (Todd Zullinger's message of "Mon, 19 Oct 2026 19:47:24 -0400")
Todd Zullinger <tmz@pobox.com> writes:
> Is it worth using `macos-latest` instead of `macos-26` and
> letting those jobs move along with the current macOS runner
> as it changes?
I am somewhat torn. Being explicit on both ends would make it
consistent between .gitlab-ci.yml and .github/workflows/main.yml so
that we can more easily compare similar execution between the CI
services offered at two sites. If we could set to a symbolic name
like "latest" and "oldest-still-supported" on both sites, I would
probably choose that in an instant, though.
next prev parent reply other threads:[~2026-10-20 1:14 UTC|newest]
Thread overview: 14+ 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
2026-10-19 7:12 ` Patrick Steinhardt
2026-10-19 18:00 ` Junio C Hamano
2026-10-19 19:41 ` [PATCH v2] " Junio C Hamano
2026-10-19 23:47 ` Todd Zullinger
2026-10-20 0:30 ` brian m. carlson
2026-10-20 0:54 ` Todd Zullinger
2026-10-20 1:14 ` Junio C Hamano [this message]
2026-10-20 5:50 ` Patrick Steinhardt
2026-10-20 14:16 ` Junio C Hamano
2026-10-20 4:25 ` [PATCH v3] " Junio C Hamano
2026-10-20 15:58 ` [PATCH v4] github-ci: update macos jobs from macos-14 Junio C Hamano
2026-10-20 17: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=xmqqpkx5yxz4.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
--cc=tmz@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