From: Patrick Steinhardt <ps@pks.im>
To: Tuomas Ahola <taahol@utu.fi>
Cc: Carlo Arenas <carenas@gmail.com>,
git@vger.kernel.org, Ed Maste <emaste@freebsd.org>
Subject: Re: Is anybody using .cirrus.yml?
Date: Wed, 4 Nov 2026 13:25:04 +0100 [thread overview]
Message-ID: <auskIPBRorDxDj6N@pks.im> (raw)
In-Reply-To: <20261104095752.2rs5_%taahol@utu.fi>
On Wed, Nov 04, 2026 at 11:57:52AM +0200, Tuomas Ahola wrote:
> Carlo Arenas <carenas@gmail.com> wrote:
>
> > On Mon, Nov 2, 2026 at 11:41 PM Patrick Steinhardt <ps@pks.im> wrote:
> >
> > > Anyway, if nobody runs it anymore we should remove it. But let's wait a
> > > few days for Carlo to answer in case he still does have a usecase for
> > > it before we send a patch to drop it.
> >
> > Thanks, but there is no reason to keep that file around AFAIK.
> >
> > Carlo
>
> Thanks both. May I have your acks please?
I think it would help if you sent this as a separate patch. Otherwise,
this patch here is going to be very hard to discover for anybody who
isn't reading this thread.
> -----8<-----
> Subject: [PATCH] CI: delete defunct Cirrus CI configuration
s/CI:/ci:/
> Since b5a9d7afcd (CI: add FreeBSD CI support via Cirrus-CI,
> 2019-12-20), .cirrus.yml has powered Git's VM-based FreeBSD CI.
>
> However, with the shutdown of Cirrus CI on 2026-06-01, there
> don't seem to be any drop-in solutions available to support our
> usecase---while there exist tools in general to run Cirrus pipelines
The three dashes are a bit funny, but okay.
> locally, managing FreeBSD VMs doesn't appear to be covered.
>
> That renders .cirrus.yml completely nonfunctional. Delete it.
>
> Signed-off-by: Tuomas Ahola <taahol@utu.fi>
Other than that this looks good to me. As said though, might make sense
to send this via a separate thread so that it becomes disocverable.
Patrick
next prev parent reply other threads:[~2026-11-04 12:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 20:41 Is anybody using .cirrus.yml? Tuomas Ahola
2026-11-03 7:41 ` Patrick Steinhardt
2026-11-04 0:05 ` Carlo Arenas
2026-11-04 9:57 ` Tuomas Ahola
2026-11-04 12:25 ` Patrick Steinhardt [this message]
2026-11-04 18:01 ` Tuomas Ahola
2026-11-04 18:03 ` Ben Knoble
2026-11-04 18:20 ` 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=auskIPBRorDxDj6N@pks.im \
--to=ps@pks.im \
--cc=carenas@gmail.com \
--cc=emaste@freebsd.org \
--cc=git@vger.kernel.org \
--cc=taahol@utu.fi \
/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