From 826d56d743fe15805cc004e10c1ee5b4fc0f69a9 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Tue, 26 Mar 2013 12:02:28 -0700 Subject: ref-manual: Active voice applied to "Debugging" section. (From yocto-docs rev: 891d6b7eed39c457334ed0956d41f4c873392855) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/technical-details.xml | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) (limited to 'documentation/ref-manual/technical-details.xml') diff --git a/documentation/ref-manual/technical-details.xml b/documentation/ref-manual/technical-details.xml index 07427b4c9c..73d27c40ce 100644 --- a/documentation/ref-manual/technical-details.xml +++ b/documentation/ref-manual/technical-details.xml @@ -529,22 +529,22 @@ Whenever a shared state package is written out, so is a corresponding .siginfo file. - This practice results in a pickled python database of all + This practice results in a pickled Python database of all the metadata that went into creating the hash for a given shared state package. - If BitBake is run with the --dump-signatures + If you run BitBake with the --dump-signatures (or -S) option, BitBake dumps out .siginfo files in the stamp directory for every task it would have executed instead of building the specified target package. There is a bitbake-diffsigs command that - can process these .siginfo files. - If one file is specified, it will dump out the dependency + can process .siginfo files. + If you specify one of these files, BitBake dumps out the dependency information in the file. - If two files are specified, it will compare the two files and dump out + If you specify two files, BitBake compares the two files and dumps out the differences between the two. - This allows the question of "What changed between X and Y?" to be - answered easily. + This more easily helps answer the question of "What + changed between X and Y?" -- cgit v1.2.3-54-g00ecf