From 47ca2108e10c1d179751fa5eefb2c8638dff8878 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Tue, 25 Feb 2014 19:02:27 -0600 Subject: ref-manual: Added BUILDHISTORY_COMMIT to glossary. (From yocto-docs rev: 8b1defdff2aaebac90b8338d6694764cff185083) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/ref-variables.xml | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml index 861be8d2a7..3928a1fa42 100644 --- a/documentation/ref-manual/ref-variables.xml +++ b/documentation/ref-manual/ref-variables.xml @@ -896,6 +896,34 @@ + BUILDHISTORY_COMMIT + + + When inheriting the + buildhistory + 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 + buildhistory + 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". + + + + By default, the buildhistory class + does not commit the build history output in a local + Git repository: + + BUILDHISTORY_COMMIT ?= "0" + + + + + BUILDHISTORY_DIR -- cgit v1.2.3-54-g00ecf