From 044a8f9e6a0cb5ffe0e97e62403bd077628e9924 Mon Sep 17 00:00:00 2001
From: Scott Rifenbark <scott.m.rifenbark@intel.com>
Date: Mon, 10 Dec 2012 16:47:27 -0600
Subject: Documentation: poky-ref-manual - Updated STAMPS directory information

The STAMPS directory is now structured as
build/tmp/stamps/$MULTIMACH_TARGET_SYS/<extended_PN>/$PV.
There were three areas in the manual that needed adjusting
to reflect this change.

(From yocto-docs rev: 1f8d64ecfa8e060680a90f9c6cc5f69554328da5)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
 documentation/poky-ref-manual/ref-bitbake.xml | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

(limited to 'documentation/poky-ref-manual/ref-bitbake.xml')

diff --git a/documentation/poky-ref-manual/ref-bitbake.xml b/documentation/poky-ref-manual/ref-bitbake.xml
index b641d5cff9..4d4b9d6188 100644
--- a/documentation/poky-ref-manual/ref-bitbake.xml
+++ b/documentation/poky-ref-manual/ref-bitbake.xml
@@ -219,9 +219,8 @@
 
         <para>
             As each task completes, a timestamp is written to the directory specified by the
-            <filename><link linkend='var-STAMP'>STAMP</link></filename> variable (usually
-            <filename>build/tmp/stamps/*/</filename>).
-            On subsequent runs, BitBake looks at the <filename>/build/tmp/stamps</filename>
+            <filename><link linkend='var-STAMP'>STAMP</link></filename> variable.
+            On subsequent runs, BitBake looks within the <filename>/build/tmp/stamps</filename>
             directory and does not rerun
             tasks that are already completed unless a timestamp is found to be invalid.
             Currently, invalid timestamps are only considered on a per
-- 
cgit v1.2.3-54-g00ecf