All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Cochran <yocto@mindchasers.com>
To: Yocto discussion list <yocto@yoctoproject.org>
Subject: [PATCH] Yocto Project Dev Manual - bad reference in dev-manual-common-tasks.xml
Date: Fri, 13 Apr 2012 17:59:46 -0400	[thread overview]
Message-ID: <4F88A1D2.6070703@mindchasers.com> (raw)

A reference to meta/recipes-sato/tasks/task-poky.bb is made as a good 
example of a task; however, this file / recipe doesn't exist.  I 
replaced it with meta/recipes-core/tasks/task-core-boot.bb, which I 
think is a both useful and basic example to consider.

Signed-off-by: Robert Cochran<yocto@mindchasers.com>

---
  .../dev-manual/dev-manual-common-tasks.xml         |    2 +-
  1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml 
b/documentation/dev-manual/dev-manual-common-tasks.xml
index a32085d..a81b656 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -495,7 +495,7 @@
                  For complex custom images, the best approach is to 
create a custom task package
                  that is used to build the image or images.
                  A good example of a tasks package is
-                <filename>meta/recipes-sato/tasks/task-poky.bb</filename>.
+ 
<filename>meta/recipes-core/tasks/task-core-boot.bb</filename>
                  The
                  <filename><ulink 
url='&YOCTO_DOCS_REF_URL;#var-PACKAGES'>PACKAGES</ulink></filename>
                  variable lists the task packages to build along with 
the complementary
-- 
1.7.5.4


             reply	other threads:[~2012-04-13 21:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-13 21:59 Bob Cochran [this message]
2012-04-16 14:01 ` [PATCH] Yocto Project Dev Manual - bad reference in dev-manual-common-tasks.xml Rifenbark, Scott M

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=4F88A1D2.6070703@mindchasers.com \
    --to=yocto@mindchasers.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 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.