From 734d58c5617eae8c2dfb6fdc4d020a31480998c9 Mon Sep 17 00:00:00 2001 From: Paul Eggleton Date: Tue, 2 Oct 2012 08:41:40 -0700 Subject: [PATCH] documentation: dev-manual - Wording changes for bumping PR I edited the patch from Paul a bit here to conform to the style of writing plus to make things clearer. (From yocto-docs rev: 87abf857cfcd8a0d78a48322fbe9ac5395b6ad30) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-common-tasks.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 8d053b3f53..96def5895f 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -1538,11 +1538,11 @@ PR variable needs to be increased (or "bumped") as part of that commit. - This means that for new recipes you must be sure to add the PR - variable and set its initial value equal to "r0". - Failing to define PR makes it easy to miss when you bump a package. - Note that you can only use integer values following the "r" in the - PR variable. + For new recipes you should add the PR + variable and set its initial value equal to "r0", which is the default. + Even though the default value is "r0", the practice of adding it to a new recipe makes + it harder to forget to bump the variable when you make changes + to the recipe in future.