summaryrefslogtreecommitdiffstats
path: root/documentation/poky-ref-manual/ref-bitbake.xml
diff options
context:
space:
mode:
authorRobert P. J. Day <rpjday@crashcourse.ca>2012-03-26 09:45:25 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-03-26 23:30:28 +0100
commit45bfc3e18971360177a2a8fc309dc7bf8465ef9a (patch)
tree4dc84919b316c3f05313956c5ba0301182be2706 /documentation/poky-ref-manual/ref-bitbake.xml
parentdf7e75fff3de897c0f473d8f774ccf9c484ee8f9 (diff)
downloadpoky-45bfc3e18971360177a2a8fc309dc7bf8465ef9a.tar.gz
documentation/poky-ref-manual: changed "STAMPS" to "STAMP"
Variable was incorrect in the manual. (From yocto-docs rev: d1ddb06cdcec48ab64df3a03f3ef845da0b13c80) Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> 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/ref-bitbake.xml')
-rw-r--r--documentation/poky-ref-manual/ref-bitbake.xml4
1 files changed, 2 insertions, 2 deletions
diff --git a/documentation/poky-ref-manual/ref-bitbake.xml b/documentation/poky-ref-manual/ref-bitbake.xml
index fa8c624c1c..663634b790 100644
--- a/documentation/poky-ref-manual/ref-bitbake.xml
+++ b/documentation/poky-ref-manual/ref-bitbake.xml
@@ -215,9 +215,9 @@
215 215
216 <para> 216 <para>
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-STAMPS'>STAMPS</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>STAMPS</filename> directory and does not rerun 220 On subsequent runs, BitBake looks at the <filename>STAMP</filename> directory and does not rerun
221 tasks that are already completed unless a timestamp is found to be invalid. 221 tasks that are already completed unless a timestamp is found to be invalid.
222 Currently, invalid timestamps are only considered on a per 222 Currently, invalid timestamps are only considered on a per
223 <filename>.bb</filename> file basis. 223 <filename>.bb</filename> file basis.