From: "Chao Li" <lichao@loongson.cn>
To: devel@edk2.groups.io
Cc: sean.brogan@microsoft.com, Bret.Barkelew@microsoft.com,
michael.d.kinney@intel.com, gaoliming@byosoft.com.cn
Subject: [PATCH] .pytool: Fix python command error in self introduction doc
Date: Fri, 22 Apr 2022 15:44:27 +0800 [thread overview]
Message-ID: <20220422074427.3133585-1-lichao@loongson.cn> (raw)
Fix misspelling of word "Prerequisites".
In the step 5 of the Prerequisites section, the python command was missing
the "-r" option, what the command really meant was to install from the given
requirements file, so fix that.
Cc: sean.brogan@microsoft.com
Cc: Bret.Barkelew@microsoft.com
Cc: michael.d.kinney@intel.com
Cc: gaoliming@byosoft.com.cn
Signed-off-by: Chao Li <lichao@loongson.cn>
---
.pytool/Readme.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/.pytool/Readme.md b/.pytool/Readme.md
index e0d07f3170..9c7b7f9abb 100644
--- a/.pytool/Readme.md
+++ b/.pytool/Readme.md
@@ -82,7 +82,7 @@ easily and consistently running locally and in a cloud ci environment. To do
that a few steps should be followed. Details of EDKII Tools can be found in the
[docs folder here](https://github.com/tianocore/edk2-pytool-extensions/tree/master/docs)
-### Prerequisets
+### Prerequisites
1. A supported toolchain (others might work but this is what is tested and validated)
* Windows 10:
@@ -95,7 +95,7 @@ that a few steps should be followed. Details of EDKII Tools can be found in the
2. Python 3.7.x or newer on path
3. git on path
4. Recommended to setup and activate a python virtual environment
-5. Install the requirements `pip install --upgrade pip-requirements.txt`
+5. Install the requirements `pip install --upgrade -r pip-requirements.txt`
### Running CI
--
2.27.0
next reply other threads:[~2022-04-22 7:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 7:44 Chao Li [this message]
2022-04-25 1:04 ` 回复: [PATCH] .pytool: Fix python command error in self introduction doc gaoliming
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=20220422074427.3133585-1-lichao@loongson.cn \
--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