Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [for-denzil][Fedora 18 fixes][PATCH 1/4] bison: move remove-gets.patch to BASE_SRC_URI, it's needed for bison-native too if host has (e)glibc-2.16
Date: Tue, 15 Jan 2013 12:18:58 -0800	[thread overview]
Message-ID: <50F5B9B2.20909@intel.com> (raw)
In-Reply-To: <1358241880-3921-1-git-send-email-koen@dominion.thruhere.net>

Hi Koen,

Thanks for these patches. With denzil 1.2.2 just having gone through 
final QA fullpass testing, the team has decided during the Technical 
Team Meeting today that we will not hold up the 1.2.2 release further, 
but instead perform the usual Autobuilder testing on them and submit 
them to the tip of the denzil branch.

So these patches (as well as Matthew McClintock's recent denzil patches) 
will not be included in 1.2.2 but I will work to get them into the 
denzil branch, so they are easily available to the folks who will need them.

Scott

-- 
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center



      parent reply	other threads:[~2013-01-15 20:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-15  9:24 [for-denzil][Fedora 18 fixes][PATCH 1/4] bison: move remove-gets.patch to BASE_SRC_URI, it's needed for bison-native too if host has (e)glibc-2.16 Koen Kooi
2013-01-15  9:24 ` [for-denzil][Fedora 18 fixes][PATCH 2/4] libtasn1: Update to 2.12 Koen Kooi
2013-01-15  9:24 ` [for-denzil][Fedora 18 fixes][PATCH 3/4] libtasn1: fix build with automake 1.12 Koen Kooi
2013-01-15  9:24 ` [for-denzil][Fedora 18 fixes][PATCH 4/4] libtasn1: Upgrade to 2.13 Koen Kooi
2013-01-15 20:18 ` Scott Garman [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=50F5B9B2.20909@intel.com \
    --to=scott.a.garman@intel.com \
    --cc=openembedded-core@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