From: Yonghong Zhu <yonghong.zhu@intel.com>
To: edk2-devel@lists.01.org
Cc: Liming Gao <liming.gao@intel.com>,
Michael Kinney <michael.d.kinney@intel.com>,
Kevin W Shaw <kevin.w.shaw@intel.com>
Subject: [Patch] DSC Spec: Fix a typo error "enty" to "entry"
Date: Tue, 2 Jan 2018 10:17:29 +0800 [thread overview]
Message-ID: <1514859449-9988-1-git-send-email-yonghong.zhu@intel.com> (raw)
Cc: Liming Gao <liming.gao@intel.com>
Cc: Michael Kinney <michael.d.kinney@intel.com>
Cc: Kevin W Shaw <kevin.w.shaw@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Yonghong Zhu <yonghong.zhu@intel.com>
---
2_dsc_overview/23_[defines]_section_processing.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/2_dsc_overview/23_[defines]_section_processing.md b/2_dsc_overview/23_[defines]_section_processing.md
index 95c2893..a7e8680 100644
--- a/2_dsc_overview/23_[defines]_section_processing.md
+++ b/2_dsc_overview/23_[defines]_section_processing.md
@@ -53,11 +53,11 @@ The format for entries in this section is:
`Name = Value`
If the `PREBUILD` and/or `POSTBUILD` entries are specified, value must be a
tool that can be executed. If the value contains space characters, then the
-value must be a quoted string. The `PREBUILD` and `POSTBUILD` enty support
+value must be a quoted string. The `PREBUILD` and `POSTBUILD` entry support
multiple arguments, and tool will convert the arguments that are WORKSPACE or
PACKAGES_PATH relative paths to absolute paths. Quotes may be used for arguments
that have spaces or special characters. The `build` tool suspends processing of
the DSC file if the `PREBUILD` entry is present, calls the script, and either
terminates or continues processing the DSC file depending on the exit code from
--
2.6.1.windows.1
next reply other threads:[~2018-01-02 2:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 2:17 Yonghong Zhu [this message]
2018-01-03 5:07 ` [Patch] DSC Spec: Fix a typo error "enty" to "entry" 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=1514859449-9988-1-git-send-email-yonghong.zhu@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