From: Eric Benard <eric@eukrea.com>
To: openembedded-devel@lists.openembedded.org
Subject: [PATCH] usermanual : update note about PR
Date: Sun, 17 Jan 2010 22:50:17 +0100 [thread overview]
Message-ID: <1263765017-12302-1-git-send-email-eric@eukrea.com> (raw)
In-Reply-To: <1263763723.5353.16.camel@mattotaupa.wohnung.familie-menzel.net>
quoting Koen Kooi : Please don't set variables to the current default
value, but leave them out. We had tons of problems with vars getting
copy/paste where the default changed and we had to manually fix those
(e.g. efl.bbclass still pokes needlessly at PACKAGES).
Signed-off-by: Eric Benard <eric@eukrea.com>
---
docs/usermanual/chapters/recipes.xml | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/usermanual/chapters/recipes.xml b/docs/usermanual/chapters/recipes.xml
index cad1d80..30364c0 100644
--- a/docs/usermanual/chapters/recipes.xml
+++ b/docs/usermanual/chapters/recipes.xml
@@ -323,9 +323,9 @@ mv fixed.recipe.bb myrecipe.bb</screen></para>
then the default value of "r0" is used.</para>
<para><note>
- <para>It is good practice to always define PR in your recipes, even
- for the <emphasis>"r0"</emphasis> release, so that when editing the
- recipe it is clear that the PR number needs to be updated.</para>
+ <para>As PR is set to "r0" as a default, it must not be defined at the
+ creation of the recipe. When editing the recipe for the first time, the
+ PR variable must be defined to "r1".</para>
<para>You should always increment PR when modifying a recipe.
Sometimes this can be avoided if the change will have no effect on the
--
1.6.3.3
next prev parent reply other threads:[~2010-01-17 21:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-17 20:32 [PATCH] barebox: Add recipe for this new bootloader Eric Benard
2010-01-17 20:51 ` Eric Bénard
2010-01-17 21:02 ` Koen Kooi
2010-01-17 21:28 ` Paul Menzel
2010-01-17 21:50 ` Eric Benard [this message]
2010-01-17 22:11 ` [PATCH] usermanual : update note about PR Frans Meulenbroeks
2010-01-18 9:24 ` Eric Bénard
2010-01-18 16:03 ` Rolf Leggewie
2010-01-18 0:31 ` Rolf Leggewie
2010-01-17 21:53 ` [PATCH] barebox: Add recipe for this new bootloader Frans Meulenbroeks
2010-01-17 23:06 ` Mike Westerhof
2010-01-18 0:22 ` Rolf Leggewie
2010-01-18 13:10 ` Phil Blundell
2010-01-18 14:28 ` Richard Purdie
2010-01-18 16:24 ` include default PR or not (was: [PATCH] barebox: Add recipe for this new bootloader) Rolf Leggewie
2010-01-21 22:53 ` Phil Blundell
2010-01-22 7:52 ` Frans Meulenbroeks
2010-01-22 16:13 ` Khem Raj
2010-01-24 10:20 ` include default PR or not Koen Kooi
2010-01-23 21:11 ` Rolf Leggewie
2010-01-19 20:44 ` [PATCH] barebox: Add recipe for this new bootloader Eric Bénard
2010-01-21 23:07 ` Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1263765017-12302-1-git-send-email-eric@eukrea.com \
--to=eric@eukrea.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox