ref-manual: Added BUILDHISTORY_COMMIT to glossary.

(From yocto-docs rev: 8b1defdff2aaebac90b8338d6694764cff185083)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2014-02-25 19:02:27 -06:00
committed by Richard Purdie
parent f3927f3271
commit 47ca2108e1

View File

@@ -896,6 +896,34 @@
</glossdef>
</glossentry>
<glossentry id='var-BUILDHISTORY_COMMIT'><glossterm>BUILDHISTORY_COMMIT</glossterm>
<glossdef>
<para>
When inheriting the
<link linkend='ref-classes-buildhistory'><filename>buildhistory</filename></link>
class, specifies whether or not to commit the build
history output in a local Git repository.
If set to "1", this local repository will be maintained
automatically by the
<filename>buildhistory</filename>
class and a commit will be created on every
build for changes to each top-level subdirectory of the
build history output (images, packages, and sdk).
If you want to track changes to build history over
time, you should set this value to "1".
</para>
<para>
By default, the <filename>buildhistory</filename> class
does not commit the build history output in a local
Git repository:
<literallayout class='monospaced'>
BUILDHISTORY_COMMIT ?= "0"
</literallayout>
</para>
</glossdef>
</glossentry>
<glossentry id='var-BUILDHISTORY_DIR'><glossterm>BUILDHISTORY_DIR</glossterm>
<glossdef>
<para>