From: Bernhard Guillon <Bernhard.Guillon@opensimpad.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC]: Remove #####...##### lines
Date: Sun, 03 May 2009 18:49:12 +0200 [thread overview]
Message-ID: <49FDCB08.4010803@opensimpad.org> (raw)
In-Reply-To: <ac9c93b10905030918t25211118yc27bb1177f1e65cb@mail.gmail.com>
Frans Meulenbroeks wrote:
> I do agree that PR = "r0" in a recipe should be ok. (actually I think
> that unaware of this I violated that rule a number of times :-) )
>
>
I like PR = "r0"
Else it is easy to forget to bump it on updates. The manual also mention
it [1].
best regards
Bernhard Guillon
1 http://docs.openembedded.org/usermanual/usermanual.html#recipes_versioning
next prev parent reply other threads:[~2009-05-03 16:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-03 12:55 [RFC]: Remove #####...##### lines Leon Woestenberg
2009-05-03 13:21 ` Philip Balister
2009-05-03 13:40 ` Mike (mwester)
2009-05-03 16:18 ` Frans Meulenbroeks
2009-05-03 16:49 ` Bernhard Guillon [this message]
2009-05-05 20:29 ` Denys Dmytriyenko
2009-05-05 20:47 ` Phil Blundell
2009-05-16 23:56 ` Leon Woestenberg
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=49FDCB08.4010803@opensimpad.org \
--to=bernhard.guillon@opensimpad.org \
--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