From: Kang Kai <kai.kang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] Update eglibc 2.13 to latest svn revision
Date: Wed, 16 Nov 2011 18:36:10 +0800 [thread overview]
Message-ID: <cover.1321439619.git.kai.kang@windriver.com> (raw)
Hi All,
I am not sure whether it is the right time to update eglibc, but sync with
upstream with latest rivision.
The following changes since commit fa81f8dfb7a342e355b608aa4204cf23ed2b251c:
mime.bbclass: fix typo (2011-11-15 12:05:30 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib kangkai/update-pkgs
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kangkai/update-pkgs
Kang Kai (1):
eglibc_2.13: update SRCREV
.../conf/distro/include/distro_tracking_fields.inc | 3 +
.../eglibc/eglibc-2.13/glibc_bug_fix_12454.patch | 179 --------------------
meta/recipes-core/eglibc/eglibc_2.13.bb | 5 +-
3 files changed, 5 insertions(+), 182 deletions(-)
delete mode 100644 meta/recipes-core/eglibc/eglibc-2.13/glibc_bug_fix_12454.patch
--
1.7.5.4
next reply other threads:[~2011-11-16 10:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 10:36 Kang Kai [this message]
2011-11-16 10:36 ` [PATCH 1/1] eglibc_2.13: update SRCREV Kang Kai
2011-11-25 0:07 ` Richard Purdie
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=cover.1321439619.git.kai.kang@windriver.com \
--to=kai.kang@windriver.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