summaryrefslogtreecommitdiffstats
path: root/documentation/poky-ref-manual
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-03-26 09:48:58 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-03-26 23:30:29 +0100
commit5df1753a152b8c374d74cfe521d20af0eb66420c (patch)
tree97d9eea97bbf71203744f65db22a00b298f092dd /documentation/poky-ref-manual
parent45bfc3e18971360177a2a8fc309dc7bf8465ef9a (diff)
downloadpoky-5df1753a152b8c374d74cfe521d20af0eb66420c.tar.gz
documentation/poky-ref-manual/ref-bitbake.xml: Fixed directory name
The /build/tmp/stamps directory was incorrectly referred to as the "STAMP" directory. Fixed it. (From yocto-docs rev: e434b3d555f7bea0b4576c6cf0d638e3e3fe664c) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/poky-ref-manual')
-rw-r--r--documentation/poky-ref-manual/ref-bitbake.xml3
1 files changed, 2 insertions, 1 deletions
diff --git a/documentation/poky-ref-manual/ref-bitbake.xml b/documentation/poky-ref-manual/ref-bitbake.xml
index 663634b790..523caf7090 100644
--- a/documentation/poky-ref-manual/ref-bitbake.xml
+++ b/documentation/poky-ref-manual/ref-bitbake.xml
@@ -217,7 +217,8 @@
217 As each task completes, a timestamp is written to the directory specified by the 217 As each task completes, a timestamp is written to the directory specified by the
218 <filename><link linkend='var-STAMP'>STAMP</link></filename> variable (usually 218 <filename><link linkend='var-STAMP'>STAMP</link></filename> variable (usually
219 <filename>build/tmp/stamps/*/</filename>). 219 <filename>build/tmp/stamps/*/</filename>).
220 On subsequent runs, BitBake looks at the <filename>STAMP</filename> directory and does not rerun 220 On subsequent runs, BitBake looks at the <filename>/build/tmp/stamps</filename>
221 directory and does not rerun
221 tasks that are already completed unless a timestamp is found to be invalid. 222 tasks that are already completed unless a timestamp is found to be invalid.
222 Currently, invalid timestamps are only considered on a per 223 Currently, invalid timestamps are only considered on a per
223 <filename>.bb</filename> file basis. 224 <filename>.bb</filename> file basis.