From be0fb616e64e54ae3e2420249f21f4edfd97d648 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Wed, 3 Aug 2016 17:44:53 -0700 Subject: bitbake-user-manual: Formatted all "flags" to be consistent Fixes [YOCTO #10071] The use of any flags throughout the manual was very inconsistent. I changed all references to any named flag in the text to be formatted as code and to be enclosed in square brackets. Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- doc/bitbake-user-manual/bitbake-user-manual-execution.xml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'doc/bitbake-user-manual/bitbake-user-manual-execution.xml') diff --git a/doc/bitbake-user-manual/bitbake-user-manual-execution.xml b/doc/bitbake-user-manual/bitbake-user-manual-execution.xml index b1b72e0aa..7b4459c95 100644 --- a/doc/bitbake-user-manual/bitbake-user-manual-execution.xml +++ b/doc/bitbake-user-manual/bitbake-user-manual-execution.xml @@ -596,7 +596,7 @@ "Checksums (Signatures)" section for information). It is also possible to append extra metadata to the stamp using - the "stamp-extra-info" task flag. + the [stamp-extra-info] task flag. For example, OpenEmbedded uses this flag to make some tasks machine-specific. @@ -653,7 +653,8 @@ It is possible to have functions run before and after a task's main function. - This is done using the "prefuncs" and "postfuncs" flags of the task + This is done using the [prefuncs] + and [postfuncs] flags of the task that lists the functions to run. -- cgit 1.2.3-korg