From f7cce1bb9169da59e8b4463b1133f5bc97eb9d98 Mon Sep 17 00:00:00 2001 From: Paul Eggleton Date: Mon, 2 Jul 2012 10:40:21 +0100 Subject: shared state memory -> shared state cache "shared state cache" is the generally accepted term for this. (From yocto-docs rev: a15f629afe46e7217182a1ac077ab59641be9a8c) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-kernel-appendix.xml | 2 +- documentation/poky-ref-manual/technical-details.xml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) (limited to 'documentation') diff --git a/documentation/dev-manual/dev-manual-kernel-appendix.xml b/documentation/dev-manual/dev-manual-kernel-appendix.xml index 962ac0bfb1..d33b77580c 100644 --- a/documentation/dev-manual/dev-manual-kernel-appendix.xml +++ b/documentation/dev-manual/dev-manual-kernel-appendix.xml @@ -679,7 +679,7 @@ The OpenEmbedded build system recognizes this kernel as linux-yocto. Thus, the following commands from the shell in which you previously sourced the - environment initialization script cleans the shared state memory and the + environment initialization script cleans the shared state cache and the WORKDIR directory and then builds and launches menuconfig: diff --git a/documentation/poky-ref-manual/technical-details.xml b/documentation/poky-ref-manual/technical-details.xml index a63943e0c6..4cc1a7b395 100644 --- a/documentation/poky-ref-manual/technical-details.xml +++ b/documentation/poky-ref-manual/technical-details.xml @@ -525,7 +525,7 @@ Invalidating Shared State - The shared state code uses checksums and shared state memory + The shared state code uses checksums and shared state cache to avoid unnecessarily rebuilding tasks. As with all schemes, this one has some drawbacks. It is possible that you could make implicit changes that are not factored -- cgit v1.2.3-54-g00ecf