From: leonardo.sandoval.gonzalez@linux.intel.com
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 1/3] bitbake-user-manual/bitbake-user-manual: remove YP as build system
Date: Mon, 2 Oct 2017 08:38:47 -0700 [thread overview]
Message-ID: <20171002153849.24922-1-leonardo.sandoval.gonzalez@linux.intel.com> (raw)
From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
YP is not a build system, so it can not be used as build system example.
Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
---
doc/bitbake-user-manual/bitbake-user-manual-intro.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/bitbake-user-manual/bitbake-user-manual-intro.xml b/doc/bitbake-user-manual/bitbake-user-manual-intro.xml
index ca7f7246..08d9afdf 100644
--- a/doc/bitbake-user-manual/bitbake-user-manual-intro.xml
+++ b/doc/bitbake-user-manual/bitbake-user-manual-intro.xml
@@ -440,7 +440,7 @@
Build Checkout:</emphasis>
A final possibility for getting a copy of BitBake is that it
already comes with your checkout of a larger Bitbake-based build
- system, such as Poky or Yocto Project.
+ system, such as Poky.
Rather than manually checking out individual layers and
gluing them together yourself, you can check
out an entire build system.
--
2.12.3
next reply other threads:[~2017-10-02 15:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 15:38 leonardo.sandoval.gonzalez [this message]
2017-10-02 15:38 ` [PATCH 2/3] bitbake-user-manual-metadata: include a space on a append example leonardo.sandoval.gonzalez
2017-10-02 15:38 ` [PATCH 3/3] README: new readme file including main aspects of the project leonardo.sandoval.gonzalez
2017-10-02 16:02 ` akuster
2017-10-02 16:06 ` Alexander Kanavin
2017-10-02 17:04 ` akuster
2017-10-02 17:05 ` Leonardo Sandoval
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=20171002153849.24922-1-leonardo.sandoval.gonzalez@linux.intel.com \
--to=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=bitbake-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.