Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/3] Important fixes for rc3
Date: Fri, 27 Apr 2012 14:28:07 -0700	[thread overview]
Message-ID: <4F9B0F67.6010708@linux.intel.com> (raw)
In-Reply-To: <cover.1334114318.git.otavio@ossystems.com.br>

On 04/10/2012 08:19 PM, Otavio Salvador wrote:
> The patches in this set are all important IMO and I do think they
> ought to be included.
>
> The following changes since commit bde1744018afd4616e114b20ffdc21b9abddcedc:
>
>    hello-mod: Move hello-mod from meta to meta-skeleton (2012-04-10 13:16:00 +0100)
>
> are available in the git repository at:
>    git://github.com/OSSystems/oe-core master
>    https://github.com/OSSystems/oe-core/tree/HEAD
>
> Otavio Salvador (3):
>    connman: backport test script fixes
>    distrodata.bbclass: fix comment typo
>    flex: backport Debian patches to fix generated code warnings
>
>   meta/classes/distrodata.bbclass                    |    2 +-
>   .../connman/test-set-ipv4-method-api-fix.patch     |   50 +++++++++++++++++
>   .../connman/test-set-ipv6-method-api-fix.patch     |   55 ++++++++++++++++++
>   meta/recipes-connectivity/connman/connman_0.79.bb  |    4 +
>   .../flex/flex/avoid-FORTIFY-warnings.patch         |   59 ++++++++++++++++++++
>   .../flex/int-is-not-the-same-size-as-size_t.patch  |   42 ++++++++++++++
>   meta/recipes-devtools/flex/flex_2.5.35.bb          |    5 +-
>   7 files changed, 215 insertions(+), 2 deletions(-)
>   create mode 100644 meta/recipes-connectivity/connman/connman/test-set-ipv4-method-api-fix.patch
>   create mode 100644 meta/recipes-connectivity/connman/connman/test-set-ipv6-method-api-fix.patch
>   create mode 100644 meta/recipes-devtools/flex/flex/avoid-FORTIFY-warnings.patch
>   create mode 100644 meta/recipes-devtools/flex/flex/int-is-not-the-same-size-as-size_t.patch
>

Merged into OE-Core

Thanks
	Sau!



      parent reply	other threads:[~2012-04-27 21:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11  3:19 [PATCH 0/3] Important fixes for rc3 Otavio Salvador
2012-04-11  3:19 ` [PATCH 1/3] connman: backport test script fixes Otavio Salvador
2012-04-11  3:28   ` Otavio Salvador
2012-04-11  3:19 ` [PATCH 2/3] distrodata.bbclass: fix comment typo Otavio Salvador
2012-04-11  3:19 ` [PATCH 3/3] flex: backport Debian patches to fix generated code warnings Otavio Salvador
2012-04-11 10:21 ` [PATCH 0/3] Important fixes for rc3 Richard Purdie
2012-04-11 12:33   ` Otavio Salvador
2012-04-27 21:28 ` Saul Wold [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=4F9B0F67.6010708@linux.intel.com \
    --to=sgw@linux.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