From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: eglibc issuettes continued
Date: Fri, 08 Jul 2011 18:19:17 +0100 [thread overview]
Message-ID: <1310145557.20015.914.camel@rex> (raw)
In-Reply-To: <9DA5872FEF993D41B7173F58FCF6BE94DE226629@orsmsx504.amr.corp.intel.com>
On Fri, 2011-07-08 at 09:59 -0700, Kamble, Nitin A wrote:
> I sent a patch to fix /etc/localtime & /etc/rpc files. Other than that I am not seeing any issues for the eglibc recipe packaging.
I pushed:
http://git.openembedded.net/cgit.cgi/openembedded-core/commit/?id=93ce74a299832ca7f24b4ce1b951abffa0232612
to fix one of those. If there is still the localtime issue, we probably
need a patch for that one...
Cheers,
Richard
next prev parent reply other threads:[~2011-07-08 17:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 15:41 eglibc issuettes continued Phil Blundell
2011-07-08 16:49 ` Richard Purdie
2011-07-08 16:53 ` Phil Blundell
2011-07-08 16:59 ` Kamble, Nitin A
2011-07-08 17:19 ` Richard Purdie [this message]
2011-07-08 17:22 ` Kamble, Nitin A
2011-07-08 17:24 ` Richard Purdie
2011-07-08 20:53 ` Koen Kooi
2011-07-08 20:23 ` Phil Blundell
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=1310145557.20015.914.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