From 2c45a8c3ff60447fb4f73d9bca64e0f1b3332a89 Mon Sep 17 00:00:00 2001
From: Scott Rifenbark <scott.m.rifenbark@intel.com>
Date: Mon, 18 Nov 2013 06:45:42 -0800
Subject: [PATCH] dev-manual: updated the ptest section

Removed the note indicating that three specific recipes were
"ptest-enabled" for the release.  I substituted in wording that
tells the user to see if a a recipe inherits ptest as a way
of determining if the receipe is ptest-enabled.

(From yocto-docs rev: f9886957055619e9c5e9eccfe0a606e7aee275cd)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
 documentation/dev-manual/dev-manual-common-tasks.xml | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index d6f5727114..65a6b6fe33 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -902,7 +902,7 @@
             </para>
 
             <para>
-                Defining the software using a custom recipe gives you total 
+                Defining the software using a custom recipe gives you total
                 control over the contents of the image.
                 It is important to use the correct names of packages in the
                 <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-IMAGE_INSTALL'>IMAGE_INSTALL</ulink></filename>
@@ -4789,11 +4789,7 @@ the details.
             </para>
 
             <note>
-                With this release of the Yocto Project, three recipes exist
-                that are "ptest-enabled": <filename>bash</filename>,
-                <filename>glib-2.0</filename>, and
-                <filename>dbus</filename>.
-                These three recipes are Autotool-enabled.
+                A recipe is "ptest-enabled" if it inherits ptest.
             </note>
 
             <section id='adding-ptest-to-your-build'>