From: Oleksii Kurochko <oleksii.kurochko@gmail.com>
To: Roger Pau Monne <roger.pau@citrix.com>, xen-devel@lists.xenproject.org
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Anthony PERARD <anthony.perard@vates.tech>,
Michal Orzel <michal.orzel@amd.com>,
Jan Beulich <jbeulich@suse.com>, Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [PATCH for-4.21 v2 0/3] cirrus-ci: get testing working again
Date: Tue, 7 Oct 2025 15:24:21 +0200 [thread overview]
Message-ID: <0f2541de-03f7-4032-8330-55d22e31ae95@gmail.com> (raw)
In-Reply-To: <20251007070056.83423-1-roger.pau@citrix.com>
[-- Attachment #1: Type: text/plain, Size: 640 bytes --]
Hello Roger,
On 10/7/25 9:00 AM, Roger Pau Monne wrote:
> Hello,
>
> The following series fixes Cirrus-CI testing so it's fully working
> again. I request a release-ack to get those committed (once reviewed).
> The risk is very low, since they only modify Cirrus-CI code, so
> Gitlab-CI is not changed at all.
Release-Acked-By: Oleksii Kurochko<oleksii.kurochko@gmail.com>
Thanks.
~ Oleksii
>
> Roger Pau Monne (3):
> cirrus-ci: install libinotify for FreeBSD
> cirrus-ci: fix bashism in the test_script code
> cirrus-ci: bump FreeBSD version
>
> .cirrus.yml | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
[-- Attachment #2: Type: text/html, Size: 1238 bytes --]
prev parent reply other threads:[~2025-10-07 13:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 7:00 [PATCH for-4.21 v2 0/3] cirrus-ci: get testing working again Roger Pau Monne
2025-10-07 7:00 ` [PATCH for-4.21 v2 1/3] cirrus-ci: install libinotify for FreeBSD Roger Pau Monne
2025-10-07 7:00 ` [PATCH for-4.21 v2 2/3] cirrus-ci: fix bashism in the test_script code Roger Pau Monne
2025-10-07 7:00 ` [PATCH for-4.21 v2 3/3] cirrus-ci: bump FreeBSD version Roger Pau Monne
2025-10-07 13:24 ` Oleksii Kurochko [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=0f2541de-03f7-4032-8330-55d22e31ae95@gmail.com \
--to=oleksii.kurochko@gmail.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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).