public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Feng, Bob C" <bob.c.feng@intel.com>
To: edk2-devel@lists.01.org
Subject: [Patch V2 0/1] Document: Update Build spec to remove EDK related
Date: Wed,  6 Mar 2019 15:49:24 +0800	[thread overview]
Message-ID: <20190306074925.11332-1-bob.c.feng@intel.com> (raw)

V2:
Update the top level README to add the update history.

Feng, Bob C (1):
  Document: Update Build spec to remove EDK related contents

 10_post-build_imagegen_stage_-_flash/103_build_intermediate_images.md |  3 +--
 12_build_changes_and_customizations/README.md                         |  4 ++--
 4_edk_ii_build_process_overview/42_build_process_overview.md          |  6 ++----
 4_edk_ii_build_process_overview/46_file_specifications.md             | 20 +-------------------
 6_quick_start/61_environment_variables.md                             | 24 +-----------------------
 8_pre-build_autogen_stage/82_auto-generation_process.md               | 76 +++++++++++-----------------------------------------------------------------
 8_pre-build_autogen_stage/83_auto-generated_code.md                   | 43 +++++++++++--------------------------------
 8_pre-build_autogen_stage/85_auto-generated_makefiles.md              | 23 +++++++++--------------
 9_build_or_make_stage/README.md                                       |  9 ++++-----
 README.md                                                             |  1 +
 appendix_a_variables.md                                               |  3 +--
 11 files changed, 44 insertions(+), 168 deletions(-)

-- 
2.20.1.windows.1



             reply	other threads:[~2019-03-06  7:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-06  7:49 Feng, Bob C [this message]
2019-03-06  7:49 ` [Patch V2 1/1] Document: Update Build spec to remove EDK related contents Feng, Bob C
2019-03-06  8:29 ` [Patch V2 0/1] Document: Update Build spec to remove EDK related Gao, Liming
2019-03-06  8:35   ` Gao, Liming

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=20190306074925.11332-1-bob.c.feng@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