From ac6bdb4d41bb8b2e1deb78d406ce0d2afb0b8505 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Mon, 16 Jun 2014 11:45:19 +0300 Subject: dev-manual, kernel-dev: Provides some cross-reference to "clean" stuff. I scrubbed the manual set for appropriate places to reference into the do_clean* type tasks. Found and added several occurrences. (From yocto-docs rev: 01594823b1d556bc70e928af1838039cc15a816d) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/kernel-dev/kernel-dev-common.xml | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) (limited to 'documentation/kernel-dev') diff --git a/documentation/kernel-dev/kernel-dev-common.xml b/documentation/kernel-dev/kernel-dev-common.xml index 31ffa5c83c..3ab21e7077 100644 --- a/documentation/kernel-dev/kernel-dev-common.xml +++ b/documentation/kernel-dev/kernel-dev-common.xml @@ -445,10 +445,16 @@ You can edit the sources as you would any other Linux source tree. However, keep in mind that you will lose changes if you - trigger the do_fetch task for the recipe. - You can avoid triggering this task by not issuing BitBake's - cleanall, cleansstate, - or forced fetch commands. + trigger the + do_fetch + task for the recipe. + You can avoid triggering this task by not using BitBake to + run the + cleanall, + cleansstate, + or forced + fetch + commands. Also, do not modify the recipe itself while working with temporary changes or BitBake might run the fetch command depending on the -- cgit v1.2.3-54-g00ecf