sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

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 <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Paul Eggleton 2012-10-02 08:41:40 -07:00 committed by Richard Purdie
parent 371a19f684
commit 734d58c561
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
documentation/dev-manual/dev-manual-common-tasks.xml
View File

@ -1538,11 +1538,11 @@
<filename><ulink url='&YOCTO_DOCS_REF_URL;#var-PR'>PR</ulink></filename> <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-PR'>PR</ulink></filename>
variable needs to be increased variable needs to be increased
(or "bumped") as part of that commit. (or "bumped") as part of that commit.
This means that for new recipes you must be sure to add the <filename>PR</filename> For new recipes you should add the <filename>PR</filename>
variable and set its initial value equal to "r0". variable and set its initial value equal to "r0", which is the default.
Failing to define <filename>PR</filename> makes it easy to miss when you bump a package. Even though the default value is "r0", the practice of adding it to a new recipe makes
Note that you can only use integer values following the "r" in the it harder to forget to bump the variable when you make changes
<filename>PR</filename> variable. to the recipe in future.
</para> </para>
<para> <para>