From: "Ard Biesheuvel" <ardb@kernel.org>
To: Michael Kubacki <mikuback@linux.microsoft.com>
Cc: Leif Lindholm <quic_llindhol@quicinc.com>,
abner.chang@amd.com, Daniel Schaefer <daniel.schaefer@hpe.com>,
Chasel Chiu <chasel.chiu@intel.com>,
Nate DeSimone <nathaniel.l.desimone@intel.com>,
Star Zeng <star.zeng@intel.com>,
Jian J Wang <jian.j.wang@intel.com>,
Hao A Wu <hao.a.wu@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: Packages Missing CI YAML Files
Date: Tue, 2 Aug 2022 00:41:26 +0200 [thread overview]
Message-ID: <CAMj1kXGJ1R7HveanwxLiaOkN9aOS2QdVHL1OoJNR=F-BskoShA@mail.gmail.com> (raw)
In-Reply-To: <6421deaf-02b5-c1a4-eda7-95455f122d7f@linux.microsoft.com>
Hello Michael,
On Tue, 2 Aug 2022 at 00:28, Michael Kubacki
<mikuback@linux.microsoft.com> wrote:
>
> Hello Package Maintainers & Reviewers,
>
> Is it intentional that these packages do not have a .ci.yaml file?
>
> 1. EmbeddedPkg
> 2. IntelFsp2Pkg
> 3. IntelFsp2WrapperPkg
> 4. SignedCapsulePkg
> 5. SourceLevelDebugPkg
>
> This impacts CI running against these packages.
>
I'm not sure what you mean with 'intentional'. Originally, no packages
had .ci.yaml files, and over time, they were contributed for most of
the packages.
If anyone wants to contribute .ci.yaml files for these packages as
well, I would not object, so I guess it is not intentional in that
sense, as far as I am concerned. But if the policy today is that all
packages must have .ci.yaml files, I'm not sure who is on the hook to
realize that.
--
Ard.
next prev parent reply other threads:[~2022-08-01 22:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 22:27 Packages Missing CI YAML Files Michael Kubacki
2022-08-01 22:41 ` Ard Biesheuvel [this message]
2022-08-02 1:21 ` [edk2-devel] " Michael Kubacki
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='CAMj1kXGJ1R7HveanwxLiaOkN9aOS2QdVHL1OoJNR=F-BskoShA@mail.gmail.com' \
--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