From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-devel@lists.openembedded.org,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [RFC] Layers, PRINC and bbappends
Date: Thu, 16 May 2013 09:37:23 +0100 [thread overview]
Message-ID: <3292696.1H20MyJFTP@helios> (raw)
In-Reply-To: <E8F9ED28-58F5-422C-8B07-ACD8791202A1@dominion.thruhere.net>
On Thursday 16 May 2013 08:23:35 Koen Kooi wrote:
> Op 15 mei 2013, om 22:33 heeft Richard Purdie
> <richard.purdie@linuxfoundation.org> het volgende geschreven:
> > On Tue, 2013-05-14 at 09:36 +0200, Koen Kooi wrote:
> >> 2) *Never* use PRINC in type b) bbappends
> >> 3) Avoid PRINC in general
> >
> > Could we undergo some mass purge of PRINC from master branches and then
> > change the PR values once and for all in the core recipes? We could make
> > PRINC throw a bb.fatal() from that point onwards.
>
> That would be nice.
Maybe we could add some logic into the PR server that if it sees PRINC go
backwards, it could just print a warning and increment the stored PR value to
compensate? That might mean storing the previous value of PRINC if we're not
already doing that of course.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-05-16 8:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 7:36 [RFC] Layers, PRINC and bbappends Koen Kooi
2013-05-15 14:44 ` Paul Eggleton
2013-05-16 6:31 ` Koen Kooi
2013-05-16 8:29 ` Paul Eggleton
2013-05-16 8:59 ` [OE-core] " Martin Jansa
2013-05-16 9:10 ` Paul Eggleton
2013-05-16 9:29 ` Martin Jansa
2013-05-16 20:15 ` Richard Purdie
2013-05-15 20:33 ` Richard Purdie
2013-05-15 23:02 ` Paul Barker
2013-05-22 8:47 ` Paul Barker
2013-05-22 9:17 ` [OE-core] " Martin Jansa
2013-05-22 10:08 ` Paul Eggleton
[not found] ` <1369217654.6695.62.camel@phil-desktop.brightsign>
2013-05-23 2:50 ` Chris Larson
2013-05-27 12:07 ` Paul Barker
2013-05-16 6:23 ` Koen Kooi
2013-05-16 8:37 ` Paul Eggleton [this message]
2013-05-16 9:27 ` Martin Jansa
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=3292696.1H20MyJFTP@helios \
--to=paul.eggleton@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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