From: Chris Co <Christopher.Co@microsoft.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Leif Lindholm <leif.lindholm@linaro.org>,
Michael D Kinney <michael.d.kinney@intel.com>
Subject: [PATCH edk2-platforms v2 2/3] Readme.md: Remove Tabs
Date: Tue, 3 Jul 2018 02:29:37 +0000 [thread overview]
Message-ID: <20180703022925.53408-3-christopher.co@microsoft.com> (raw)
In-Reply-To: <20180703022925.53408-1-christopher.co@microsoft.com>
Fix for issue found when running patch check script.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Christopher Co <christopher.co@microsoft.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Leif Lindholm <leif.lindholm@linaro.org>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
---
Readme.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Readme.md b/Readme.md
index 73950821e4de..6ad5953093d6 100644
--- a/Readme.md
+++ b/Readme.md
@@ -171,10 +171,10 @@ $ git clone https://git.linaro.org/uefi/uefi-tools.git
$ ./uefi-tools/edk2-build.sh juno
...
------------------------------------------------------------
- aarch64 Juno (AARCH64) RELEASE pass
+ aarch64 Juno (AARCH64) RELEASE pass
------------------------------------------------------------
-pass 1
-fail 0
+pass 1
+fail 0
```
The build finishes with a summary of which platforms/targets were built, which
succeeded and which failed (and the total number of either).
--
2.16.2.gvfs.1.33.gf5370f1
next prev parent reply other threads:[~2018-07-03 2:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 2:29 [PATCH edk2-platforms v2 0/3]Readme: Add instructions to build in a Windows Environment Chris Co
2018-07-03 2:29 ` [PATCH edk2-platforms v2 1/3] Readme.md: Change line endings from LF to CLRF Chris Co
2018-07-03 2:29 ` Chris Co [this message]
2018-07-03 2:29 ` [PATCH edk2-platforms v2 3/3] Readme.md: Add instructions to build in a Windows Environment Chris Co
2018-07-03 10:24 ` Leif Lindholm
2018-07-03 18:55 ` Evan Lloyd
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=20180703022925.53408-3-christopher.co@microsoft.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