From: Michael Kinney <michael.d.kinney@intel.com>
To: edk2-devel@lists.01.org
Cc: Liming Gao <liming.gao@intel.com>,
Yonghong Zhu <yonghong.zhu@intel.com>,
Kevin W Shaw <kevin.w.shaw@intel.com>
Subject: [ edk2-BuildSpecification PATCH 0/2] Add --pcd flag to override PCD values on command line
Date: Tue, 25 Apr 2017 11:55:38 -0700 [thread overview]
Message-ID: <1493146540-13060-1-git-send-email-michael.d.kinney@intel.com> (raw)
https://bugzilla.tianocore.org/show_bug.cgi?id=480
GitHub branch for review:
* https://github.com/mdkinney/edk2-BuildSpecification/tree/Bugzilla_480_CommandLinePcdOverride
GitHub word diff view of the patches in this series:
* [1/2] https://github.com/mdkinney/edk2-BuildSpecification/commit/2bec147a4f988c97a05d93d2c113673b0e9fa2ba?w=1
* [2/2] https://github.com/mdkinney/edk2-BuildSpecification/commit/2e771af54931855a4f3ee39465e51df31312b314?w=1
Cc: Liming Gao <liming.gao@intel.com>
Cc: Yonghong Zhu <yonghong.zhu@intel.com>
Cc: Kevin W Shaw <kevin.w.shaw@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Michael Kinney <michael.d.kinney@intel.com>
Michael Kinney (2):
Clean up minor formatting issues
Add --pcd flag to override PCD values on command line
.../43_pre-build_stage_overview.md | 35 ++++++++++----------
.../45_post-build_stage.md | 12 +++----
.../82_auto-generation_process.md | 37 ++++++++++++++++++----
.../84_auto-generated_pcd_database_file.md | 34 +++++++++++---------
README.md | 1 +
appendix_d_buildexe_command/d4_usage.md | 1 +
6 files changed, 74 insertions(+), 46 deletions(-)
--
2.6.3.windows.1
next reply other threads:[~2017-04-25 18:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 18:55 Michael Kinney [this message]
2017-04-25 18:55 ` [ edk2-BuildSpecification PATCH 1/2] Clean up minor formatting issues Michael Kinney
2017-04-25 18:55 ` [ edk2-BuildSpecification PATCH 2/2] Add --pcd flag to override PCD values on command line Michael Kinney
2017-04-26 5:22 ` Zhu, Yonghong
2017-04-26 6:42 ` Kinney, Michael D
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=1493146540-13060-1-git-send-email-michael.d.kinney@intel.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