From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Oliver Steffen <osteffen@redhat.com>
Cc: devel@edk2.groups.io, "Eric Dong" <eric.dong@intel.com>,
"Liming Gao" <gaoliming@byosoft.com.cn>,
"Michael D Kinney" <michael.d.kinney@intel.com>,
"Michael Kubacki" <mikuback@linux.microsoft.com>,
"Rahul Kumar" <rahul1.kumar@intel.com>,
"Ray Ni" <ray.ni@intel.com>,
"Sean Brogan" <sean.brogan@microsoft.com>,
"Sunil V L" <sunilvl@ventanamicro.com>,
"Paweł Poławski" <ppolawsk@redhat.com>,
"Chris Fernald" <chris.fernald@outlook.com>
Subject: Re: [RESEND v1 0/1] CI: Use Fedora 37 / GCC 12 for Linux jobs
Date: Fri, 31 Mar 2023 13:11:24 +0200 [thread overview]
Message-ID: <jy4qyqybnvhlu7habwmuuqawkwdpbenbga62mmwtdcpghrqczs@j3lzjxgo5ofn> (raw)
In-Reply-To: <20230314152114.156566-1-osteffen@redhat.com>
On Tue, Mar 14, 2023 at 04:21:13PM +0100, Oliver Steffen wrote:
> Switch the CI (Linux) to use GCC 12 providied by a new Fedora 37 based
> container image.
>
> New container image: https://github.com/tianocore/containers/pull/60
>
> Test PR: https://github.com/tianocore/edk2/pull/4108
PING CI maintainers.
It got three reviews and no concerns raised.
Can we please get this merged?
The riscv folks need gcc-12 in CI to make progress.
thanks,
Gerd
next prev parent reply other threads:[~2023-03-31 11:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 15:21 [RESEND v1 0/1] CI: Use Fedora 37 / GCC 12 for Linux jobs Oliver Steffen
2023-03-14 15:21 ` [RESEND v1 1/1] CI: Use Fedora-37 (gcc12) image " Oliver Steffen
2023-03-14 18:39 ` [edk2-devel] " Rebecca Cran
2023-03-30 13:48 ` Dhaval Sharma
2023-03-31 11:10 ` Oliver Steffen
2023-04-01 18:24 ` Rebecca Cran
2023-03-31 11:11 ` Gerd Hoffmann [this message]
2023-05-06 17:29 ` [edk2-devel] [RESEND v1 0/1] CI: Use Fedora 37 / GCC 12 " Dhaval Sharma
2023-05-08 1:15 ` 回复: " gaoliming
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-list 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=jy4qyqybnvhlu7habwmuuqawkwdpbenbga62mmwtdcpghrqczs@j3lzjxgo5ofn \
--to=devel@edk2.groups.io \
/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