Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/3] perl: fix Perl5 module builds
Date: Thu, 29 Oct 2015 07:39:29 +0000	[thread overview]
Message-ID: <1446104369.4521.25.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAJTo0LY-DAxN5+wbgkOv0TsVHUWfPtJ_yJN8cBdxCx5NP5UOJg@mail.gmail.com>

On Thu, 2015-10-29 at 07:31 +0000, Burton, Ross wrote:
> On 28 October 2015 at 10:26, Jens Rehsack <rehsack@gmail.com> wrote:
>         Since it's two weeks ago since submitted and this patch series
>         fixes several problems how yocto deals with perl module
>         distributions, I'd like to get a more concrete explanation why
>         an infrastructure fix isn't validated during feature freeze
>         for branching.
>
>         None of the three patches adds a feature, they all fix broken
>         infrastructure of perl module handling in Yocto which should
>         better now validated than after branching.
>         Since after freeze the master branch might become unstable for
>         a while, I might not be able to re-submit.

>
> These patches are in the current build under consideration for merging
> in time for the Jethro release.  Sorry for the lack of feedback on
> them, this release has been cursed with autobuilder stability problems
> which have taken up a lot of our time.

Given the last round of autobuilder results, I just merged them.

Cheers,

Richard




      reply	other threads:[~2015-10-29  7:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-08 14:21 [PATCH 1/3] perl: fix Perl5 module builds Jens Rehsack
2015-10-28 10:26 ` Jens Rehsack
2015-10-29  7:31   ` Burton, Ross
2015-10-29  7:39     ` Richard Purdie [this message]

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=1446104369.4521.25.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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