On Mon, Sep 07, 2015 at 12:37:35PM +0300, Alexander Kanavin wrote:
> On 09/04/2015 05:16 PM, Khem Raj wrote:
> 
> >     I will send these patches only when oe-core is updated. Recipe
> >     moving is always controversial, and I don't want to cause confusion
> >     when the change is accepted by one side and rejected by the other.
> >
> >
> > On the contrary you can make a note in patch to destination layer citing
> > the patch for source layer being a prerequisite to be accepted.
> > Maintainers then can schedule it accordingly.
> 
> Martin, would you prefer this approach? My problem is that the gap 

yes

> between initial oe-core patch submission and their acceptance is often 
> measured in weeks and sometimes months, so the corresponding meta-oe 
> patches would be hanging in limbo, and may be easily forgotten.

I shouldn't forget them, because they will sit in patchwork's
queue or alternatively I'll cherry-pick the removal to my oe-core's
jansa/master together with these changes in meta-oe's jansa/master
branches so I'll build-test them in my Jenkins builds until it's merged
in oe-core.

It's a bit error prone, but the delay will be shorter if we do it this
way.

Full jenkins build test takes over 3 days (depending on sstate reuse,
one MACHINE can take more than 24 hours), so if I add them to
master-next after it's merged to oe-core it will take 3-6 days to
build-test them (6 days if they are sent just after current queue is
sent for build).

Regards,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com