From: "Michael Kubacki" <mikuback@linux.microsoft.com>
To: devel@edk2.groups.io
Cc: Andrew Fish <afish@apple.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Bob Feng <bob.c.feng@intel.com>,
Chris Fernald <chrisf671@gmail.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Jiewen Yao <jiewen.yao@intel.com>,
Jordan Justen <jordan.l.justen@intel.com>,
Leif Lindholm <quic_llindhol@quicinc.com>,
Liming Gao <gaoliming@byosoft.com.cn>,
Michael D Kinney <michael.d.kinney@intel.com>,
Ray Ni <ray.ni@intel.com>, Sami Mujawar <sami.mujawar@arm.com>,
Sean Brogan <sean.brogan@microsoft.com>,
Yuwei Chen <yuwei.chen@intel.com>
Subject: [PATCH v1 0/5] Update references to new edk2 build instructions
Date: Mon, 5 Dec 2022 12:28:34 -0500 [thread overview]
Message-ID: <20221205172839.2859-1-mikuback@linux.microsoft.com> (raw)
From: Michael Kubacki <michael.kubacki@microsoft.com>
Note: This series is dependent on the following TianoCore wiki
series being merged for links to resolve properly.
https://edk2.groups.io/g/devel/message/96962
New build instructions are being added to the TianoCore wiki [1]
to describe how to use relatively recent additions to the edk2 build
process - containers and Stuart.
This series updates build instructions in the edk2 repo with a link
to the new instructions page on the wiki so users are aware of the
instructions.
Content is only directly modified in the edk2 repo that is directly
replaced with corresponding content in the wiki page.
[1]: https://github.com/tianocore/tianocore.github.io/wiki
Cc: Andrew Fish <afish@apple.com>
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>
Cc: Bob Feng <bob.c.feng@intel.com>
Cc: Chris Fernald <chrisf671@gmail.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>
Cc: Jiewen Yao <jiewen.yao@intel.com>
Cc: Jordan Justen <jordan.l.justen@intel.com>
Cc: Leif Lindholm <quic_llindhol@quicinc.com>
Cc: Liming Gao <gaoliming@byosoft.com.cn>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Cc: Ray Ni <ray.ni@intel.com>
Cc: Sami Mujawar <sami.mujawar@arm.com>
Cc: Sean Brogan <sean.brogan@microsoft.com>
Cc: Yuwei Chen <yuwei.chen@intel.com>
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
Michael Kubacki (5):
.pytool/Readme.md: Add reference to new build instructions
ArmVirtPkg: Add reference to new build instructions
BaseTools: Add reference to new build instructions
EmulatorPkg: Add reference to new build instructions
OvmfPkg: Add reference to new build instructions
.pytool/Readme.md | 52 +++++++-------------
ArmVirtPkg/PlatformCI/ReadMe.md | 3 ++
BaseTools/ReadMe.rst | 13 +++--
EmulatorPkg/PlatformCI/ReadMe.md | 3 ++
OvmfPkg/PlatformCI/ReadMe.md | 3 ++
OvmfPkg/README | 5 +-
6 files changed, 40 insertions(+), 39 deletions(-)
--
2.28.0.windows.1
next reply other threads:[~2022-12-05 17:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 17:28 Michael Kubacki [this message]
2022-12-05 17:28 ` [PATCH v1 1/5] .pytool/Readme.md: Add reference to new build instructions Michael Kubacki
2022-12-05 17:28 ` [PATCH v1 2/5] ArmVirtPkg: " Michael Kubacki
2022-12-05 17:28 ` [PATCH v1 3/5] BaseTools: " Michael Kubacki
2022-12-05 17:28 ` [PATCH v1 4/5] EmulatorPkg: " Michael Kubacki
2022-12-05 17:28 ` [PATCH v1 5/5] OvmfPkg: " Michael Kubacki
2022-12-09 7:00 ` Yao, Jiewen
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=20221205172839.2859-1-mikuback@linux.microsoft.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