From: Saul Wold <sgw@linux.intel.com>
To: 'Patches and discussions about the oe-core layer'
<openembedded-core@lists.openembedded.org>
Subject: Working through the Backlog
Date: Fri, 27 Apr 2012 13:46:07 -0700 [thread overview]
Message-ID: <4F9B058F.6050705@linux.intel.com> (raw)
As many of you may have noticed, we have been working through the
backlog on this mailing list. I will sending out many Merged messages
to help track what we have pulled.
As Richard has already mentioned we are going to be moving to the newer
GCC and will be looking at updating eglibc shortly also.
I will continue to work through the backlog and send comments or putting
together a Consolidated pull over the weekend based on what's here now.
If your patch has not been pulled or somehow missed, please ping or
resend the patch.
Thanks
--
Sau!
Saul Wold
Yocto Component Wrangler @ Intel
Yocto Project / Poky Build System
reply other threads:[~2012-04-27 20:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4F9B058F.6050705@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