From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: akuster808 <akuster808@gmail.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: glibc update
Date: Wed, 03 Jan 2018 21:20:46 +0000 [thread overview]
Message-ID: <1515014446.5525.157.camel@linuxfoundation.org> (raw)
In-Reply-To: <661e1908-ae7a-3125-cc49-fc87014ee1cb@gmail.com>
On Wed, 2018-01-03 at 12:17 -0800, akuster808 wrote:
> I noticed all but the glibc updates where merged from Khem's
> toolchain-update branch. Is there an issue with the glibc update,
> was it just missed or pending more testing?
>
> I have some patches I need to submit but I don't want to chase a
> moving target.
I'm trying to test things in batches without too many moving pieces and
I'm deferring the most risky things.
Given the number of glibc upgrade issues we've had recently (think
uninative) I'm apprehensive about the glibc patches and we had a queue
of other patches which conflict. I therefore have deferred that
particular patch until I have others sorted out. We are missing the
corresponding uninative upgrade to match the glibc upgrade which is
another factor. It may all turn out to be an unfounded worry or it may
not.
We will get there but I'm also kind of enjoying greenish builds ;-)
Cheers,
Richard
prev parent reply other threads:[~2018-01-03 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 20:17 glibc update akuster808
2018-01-03 21:20 ` 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=1515014446.5525.157.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=akuster808@gmail.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