Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel@lists.openembedded.org,
	openembedded-core@lists.openembedded.org
Subject: Re: [RFC PATCH] base.bbclass: Deprecate the PRINC logic
Date: Wed, 29 May 2013 15:47:20 +0100	[thread overview]
Message-ID: <1369838840.14887.220.camel@ted> (raw)
In-Reply-To: <20130529143740.GL3192@jama>

On Wed, 2013-05-29 at 16:37 +0200, Martin Jansa wrote:
> On Wed, May 29, 2013 at 08:51:36AM -0500, Mark Hatle wrote:
> > Background:
> > 
> > At the recent TSC meeting we were discussing ways of removing the PRINC
> > in favor of the PR server, which should now be standard.  The first step
> > in this process is coming up with a simple patch that declared PRINC as
> > deprecated.  If this type of patch is successful, the block of code could
> > be replaced with a bb.error eventually.
> > 
> > It is not expected that this patch will go in by itself, but instead
> > should be coordinated with changes to the recipes in common layers such
> > as openembedded-core, meta-openembedded/meta-* and other community layers.
> 
> This doesn't say what's the process of getting all PR increments
> applied.
> 
> Should we send list of recipes and required PR increments per layer (and
> someone will sum these increments and create actual PR bump from it). Or
> will we take turns and send actual PR bump patches per layer and someone 
> will define order of layers to go in (so that we prevent many conflicts 
> while merging)?

This is something we need to figure out. The realistic process is
probably do this layer by layer. If we can batch some up together that
would obviously be better...

Cheers,

Richard



  reply	other threads:[~2013-05-29 14:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-29 13:51 [RFC PATCH] base.bbclass: Deprecate the PRINC logic Mark Hatle
2013-05-29 14:11 ` Richard Purdie
2013-05-29 14:37 ` Martin Jansa
2013-05-29 14:47   ` Richard Purdie [this message]
2013-05-29 17:00     ` [OE-core] " Otavio Salvador
2013-05-29 21:24       ` Richard Purdie

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=1369838840.14887.220.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.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