All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	xen-devel@lists.xenproject.org,
	George Dunlap <george.dunlap@citrix.com>,
	Julien Grall <julien@xen.org>,
	Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>
Subject: Re: [PATCH] CirrusCI: drop FreeBSD 12
Date: Mon, 15 Jan 2024 13:32:10 +0100	[thread overview]
Message-ID: <ZaUlynk34sJATApl@macbook> (raw)
In-Reply-To: <6528658a-5cb7-4f9b-a92d-a4ca43f6352b@suse.com>

On Mon, Jan 15, 2024 at 12:37:39PM +0100, Jan Beulich wrote:
> On 15.01.2024 12:20, Roger Pau Monné wrote:
> > On Mon, Jan 15, 2024 at 11:01:54AM +0000, Andrew Cooper wrote:
> >> On 15/01/2024 10:27 am, Roger Pau Monne wrote:
> >>> Went EOL by the end of December 2023, and the pkg repos have been shut down.
> >>>
> >>> Reported-by: Andrew Cooper <andrew.cooper3@citrix.com>
> >>> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
> >>
> >> Acked-by: Andrew Cooper <andrew.cooper3@citrix.com>
> >>
> >> We'll need to backport this, I guess ?
> > 
> > Yup, but it might not apply cleanly without the rest of the changes to
> > the file backported also.
> 
> Looks to apply fine to .18 and .17, which it what I'll queue it for.
> If and when we need it on .16 and/or .15 as well, adjusting the patch
> rather then taking further (not really) prereqs may be preferable.

We would likely need to take backports, because the versions in 15 and
16 CirrusCI file are also EOL, so I think it won't work anyway.

Thanks, Roger.


      reply	other threads:[~2024-01-15 12:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15 10:27 [PATCH] CirrusCI: drop FreeBSD 12 Roger Pau Monne
2024-01-15 11:01 ` Andrew Cooper
2024-01-15 11:20   ` Roger Pau Monné
2024-01-15 11:37     ` Jan Beulich
2024-01-15 12:32       ` Roger Pau Monné [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=ZaUlynk34sJATApl@macbook \
    --to=roger.pau@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=sstabellini@kernel.org \
    --cc=wl@xen.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 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.