From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] eglibc_2.13: update SRCREV
Date: Fri, 25 Nov 2011 00:07:30 +0000 [thread overview]
Message-ID: <1322179650.10928.44.camel@ted> (raw)
In-Reply-To: <e4edb77cfaf1aa7e5aed01ad7d279fe2a37d11d8.1321439619.git.kai.kang@windriver.com>
On Wed, 2011-11-16 at 18:36 +0800, Kang Kai wrote:
> Update eglibc 2.13 SRCREV to 15508, just to sync with upstream
> Remove glibc_bug_fix_12454.patch, because it is already merged.
>
> Signed-off-by: Kang Kai <kai.kang@windriver.com>
> ---
> .../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
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-11-25 0:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 10:36 [PATCH 0/1] Update eglibc 2.13 to latest svn revision Kang Kai
2011-11-16 10:36 ` [PATCH 1/1] eglibc_2.13: update SRCREV Kang Kai
2011-11-25 0:07 ` Richard Purdie [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=1322179650.10928.44.camel@ted \
--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