From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "openembedded-core@lists.openembedded.org" ">>" Patches and
discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFT] Glibc 2.23 and binutils 2.26
Date: Fri, 29 Jan 2016 16:14:24 +0200 [thread overview]
Message-ID: <56AB73C0.8030505@linux.intel.com> (raw)
In-Reply-To: <2747032A-1F56-4CA6-860C-484B9292A0B5@gmail.com>
On 01/17/2016 01:54 PM, Khem Raj wrote:
> upstream glibc and binutils release branches have been cut out and are being made ready for next release
> I have put together update patchset for both of them
>
> here are the branches
>
> https://github.com/kraj/openembedded-core/tree/kraj/binutils-2.26
> https://github.com/kraj/openembedded-core/tree/kraj/glibc-2.23
Hello Khem,
when are you planning to submit these?
Alex
next prev parent reply other threads:[~2016-01-29 14:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 11:54 [RFT] Glibc 2.23 and binutils 2.26 Khem Raj
2016-01-22 1:28 ` [oe] " akuster808
2016-01-27 2:11 ` ChenQi
2016-01-27 5:30 ` Khem Raj
2016-01-29 14:14 ` Alexander Kanavin [this message]
2016-01-29 14:44 ` Khem Raj
2016-01-31 8:32 ` Richard Purdie
2016-01-31 8:53 ` Khem Raj
2016-02-01 9:12 ` Richard Purdie
2016-02-01 17:02 ` 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=56AB73C0.8030505@linux.intel.com \
--to=alexander.kanavin@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