From: "Randy MacLeod" <randy.macleod@windriver.com>
To: <yocto@yoctoproject.org>
Subject: [meta-parsec][PATCH] Correct typo: crago-bitbake
Date: Wed, 26 May 2021 09:19:02 -0400 [thread overview]
Message-ID: <20210526131903.158963-1-Randy.MacLeod@windriver.com> (raw)
Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com>
---
meta-parsec/README.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-parsec/README.md b/meta-parsec/README.md
index a2736b6..6d938a6 100644
--- a/meta-parsec/README.md
+++ b/meta-parsec/README.md
@@ -75,7 +75,7 @@ to ensure maximum reproducibility.
versions of parsec recipes.
https://github.com/meta-rust/cargo-bitbake
- When you have crago-bitbake built:
+ When you have cargo-bitbake built:
1. Checkout the required version of parsec repository.
2. Run cargo-bitbake inside the repository. It will produce a BB file.
3. Create a new include file with SRC_URI and LIC_FILES_CHKSUM from the BB file.
--
2.27.0
reply other threads:[~2021-05-26 13:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-all 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=20210526131903.158963-1-Randy.MacLeod@windriver.com \
--to=randy.macleod@windriver.com \
--cc=yocto@yoctoproject.org \
/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