From: "Abner Chang" <abner.chang@hpe.com>
To: devel@edk2.groups.io
Subject: [RedfishPkg PATCH 0/4] Inital RedfishPkg
Date: Tue, 29 Sep 2020 17:47:44 +0800 [thread overview]
Message-ID: <20200929094748.8391-1-abner.chang@hpe.com> (raw)
Initial version of RedfishPkg and the CI test
on RedfishPkg.
CI Test result:
https://github.com/tianocore/edk2/pull/975
There is no components in RedfishPkg in this commit,
the further edk2 Redfish components will be committed
base on this version.
changab (4):
RedfishPkg: Initial commit of RedfishPkg.
.pytool: Add CI on RedfishPkg
.azurepipelines/templates: Add RedfishPkg to target build
edk2: Add maintainers to RedfishPkg
.../templates/pr-gate-build-job.yml | 3 +
.pytool/CISettings.py | 3 +-
Maintainers.txt | 6 ++
RedfishPkg/RedfishPkg.ci.yaml | 67 +++++++++++++++++++
RedfishPkg/RedfishPkg.dec | 18 +++++
RedfishPkg/RedfishPkg.dsc | 40 +++++++++++
6 files changed, 136 insertions(+), 1 deletion(-)
create mode 100644 RedfishPkg/RedfishPkg.ci.yaml
create mode 100644 RedfishPkg/RedfishPkg.dec
create mode 100644 RedfishPkg/RedfishPkg.dsc
--
2.17.1
next reply other threads:[~2020-09-29 10:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 9:47 Abner Chang [this message]
2020-09-29 9:47 ` [RedfishPkg PATCH 1/4] RedfishPkg: Initial commit of RedfishPkg Abner Chang
2020-09-29 9:47 ` [RedfishPkg PATCH 2/4] .pytool: Add CI on RedfishPkg Abner Chang
2020-09-29 9:47 ` [RedfishPkg PATCH 3/4] .azurepipelines/templates: Add RedfishPkg to target build Abner Chang
2020-10-15 1:57 ` [edk2-devel] " Sean
2020-10-15 2:29 ` Abner Chang
2020-09-29 9:47 ` [RedfishPkg PATCH 4/4] edk2: Add maintainers to RedfishPkg Abner Chang
2020-09-29 10:42 ` Laszlo Ersek
2020-09-29 11:23 ` Abner Chang
2020-09-30 0:58 ` 回复: [edk2-devel] " gaoliming
2020-09-30 2:48 ` Abner Chang
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=20200929094748.8391-1-abner.chang@hpe.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