From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC]: Remove #####...##### lines
Date: Tue, 05 May 2009 16:29:36 -0400 [thread overview]
Message-ID: <20090505202936.GA22698@denix.org> (raw)
In-Reply-To: <49FDCB08.4010803@opensimpad.org>
On Sun, May 03, 2009 at 06:49:12PM +0200, Bernhard Guillon wrote:
> 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].
+1 - I agree it's easy to forget to bump it, if it's not there...
--
Denys
next prev parent reply other threads:[~2009-05-05 20:35 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
2009-05-05 20:29 ` Denys Dmytriyenko [this message]
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=20090505202936.GA22698@denix.org \
--to=denis@denix.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