Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 5/5] glibc: fix false failure
Date: Wed, 13 Jul 2011 12:16:09 +0100	[thread overview]
Message-ID: <1310555769.20015.1099.camel@rex> (raw)
In-Reply-To: <5fc1498aa6920e8d07e831d10ef1efd656fbfa8b.1310497097.git.nitin.a.kamble@intel.com>

On Tue, 2011-07-12 at 12:02 -0700, nitin.a.kamble@intel.com wrote:
> From: Nitin A Kamble <nitin.a.kamble@intel.com>
> 
> do not just fail if grep does not match the locale name in the list
> 
> Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
> ---
>  meta/recipes-core/glibc/glibc.inc |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)

Merged to master, thanks.

Richard




  reply	other threads:[~2011-07-13 11:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-12 19:02 [PATCH 0/5] commits for yocto.git tree for x32 work nitin.a.kamble
2011-07-12 19:02 ` [PATCH 1/5] siteinfo.bbclass: hack for x32 nitin.a.kamble
2011-07-13  6:20   ` Khem Raj
2011-07-13 15:41     ` Kamble, Nitin A
2011-07-14 19:49       ` Khem Raj
2011-07-12 19:02 ` [PATCH 2/5] udev-172: add a newer version for newer kernel nitin.a.kamble
2011-07-13  6:22   ` Khem Raj
2011-07-13  6:59     ` Koen Kooi
2011-07-13 15:43       ` Kamble, Nitin A
2011-07-12 19:02 ` [PATCH 3/5] runqemu: support qemux32 machine nitin.a.kamble
2011-07-13  1:35   ` Bruce Ashfield
2011-07-12 19:02 ` [PATCH 4/5] kernel.bbclass: fix the broken lines nitin.a.kamble
2011-07-13 11:16   ` Richard Purdie
2011-07-12 19:02 ` [PATCH 5/5] glibc: fix false failure nitin.a.kamble
2011-07-13 11:16   ` Richard Purdie [this message]
2011-07-13 11:20 ` [PATCH 0/5] commits for yocto.git tree for x32 work Richard Purdie
2011-07-13 14:14   ` Tom Rini
2011-07-13 14:38   ` Khem Raj

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=1310555769.20015.1099.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --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