From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org, "brian m. carlson" <sandals@crustytoothpaste.net>
Subject: Re: What's cooking in git.git (Nov 2024, #09; Mon, 25)
Date: Thu, 28 Nov 2024 10:57:54 +0900 [thread overview]
Message-ID: <xmqqy114p1b1.fsf@gitster.g> (raw)
In-Reply-To: <Z0bYpiP2JDEzqJXr@pks.im> (Patrick Steinhardt's message of "Wed, 27 Nov 2024 09:30:37 +0100")
Patrick Steinhardt <ps@pks.im> writes:
> On Mon, Nov 25, 2024 at 05:07:59PM +0900, Junio C Hamano wrote:
>> * bc/ancient-ci (2024-11-01) 3 commits
>> - Add additional CI jobs to avoid accidental breakage
>> - ci: remove clause for Ubuntu 16.04
>> - gitlab-ci: switch from Ubuntu 16.04 to 20.04
>>
>> Drop support for ancient environments in various CI jobs.
>>
>> Needs review.
>> source: <20241031234934.3451390-1-sandals@crustytoothpaste.net>
>
> I've reviewed these changes in <ZyixnuBY5TcyrHEj@pks.im>, even though I
> don't feel a 100% qualified to comment on the GitHub changes. But given
> that bc/drop-ancient-libcurl-and-perl has been merged to `next` by now
> it would be nice if the above series could be merged soonish, as well,
> so that the GitLab CI is getting fixed.
Yeah, I think we saw on 'seen' what these changes do enough (at
least, it doesn't seem to break everything ;-). Let's mark it for
'next'.
Thanks.
next prev parent reply other threads:[~2024-11-28 1:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 8:07 What's cooking in git.git (Nov 2024, #09; Mon, 25) Junio C Hamano
2024-11-27 8:30 ` Patrick Steinhardt
2024-11-28 1:57 ` Junio C Hamano [this message]
2024-11-27 12:19 ` karthik nayak
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=xmqqy114p1b1.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
--cc=sandals@crustytoothpaste.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 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.