public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Michael Kinney <michael.d.kinney@intel.com>
To: edk2-devel@lists.01.org
Subject: [edk2-FdfSpecification PATCH 0/2] Allow macros in !include file paths
Date: Fri,  7 Apr 2017 19:44:42 -0700	[thread overview]
Message-ID: <1491619484-18836-1-git-send-email-michael.d.kinney@intel.com> (raw)

* Use macros in !include file paths
  https://bugzilla.tianocore.org/show_bug.cgi?id=350
* Remove illegal white space in FDF file examples

GitHub branch for review:

  https://github.com/mdkinney/edk2-FdfSpecification/tree/Bugzilla_350_MacrosInIncludes
  
GitHub branch compare against latest DRAFT for review:

  https://github.com/tianocore-docs/edk2-FdfSpecification/compare/master...mdkinney:Bugzilla_350_MacrosInIncludes


Michael Kinney (2):
  Use macros in !include file paths
  Remove illegal white space in FDF file examples

 .../22_flash_description_file_format.md            | 21 +++++++++--------
 2_fdf_design_discussion/25_[fv]_sections.md        | 12 +++++-----
 3_edk_ii_fdf_file_format/32_fdf_definition.md      | 26 +++++++++++++---------
 appendix_a_nt32pkg_flash_description_file.md       | 14 ++++++------
 4 files changed, 39 insertions(+), 34 deletions(-)

-- 
2.6.3.windows.1



             reply	other threads:[~2017-04-08  2:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-08  2:44 Michael Kinney [this message]
2017-04-08  2:44 ` [edk2-FdfSpecification PATCH 1/2] Use macros in !include file paths Michael Kinney
2017-04-08  2:44 ` [edk2-FdfSpecification PATCH 2/2] Remove illegal white space in FDF file examples Michael Kinney
2017-04-11  1:34 ` [edk2-FdfSpecification PATCH 0/2] Allow macros in !include file paths Zhu, Yonghong

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=1491619484-18836-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