From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Armin Kuster <akuster808@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Dizzy Merging
Date: Wed, 31 Dec 2014 10:26:25 +0000 [thread overview]
Message-ID: <1420021585.25779.14.camel@linuxfoundation.org> (raw)
In-Reply-To: <cover.1418663308.git.akuster808@gmail.com>
Hi Armin,
I've taken a look at the dizzy_1_7_1 branch and have merged a lot of
things. For bitbake, I took the patches into the 1.24 branch. There was
a patch missing for the PR server sync changes so I added that too,
otherwise the others didn't make sense.
For the OE-Core patches, the gcc sysroot poison one should not go in.
I'd also question the udev changes and the gcc shared work changes since
those were fairly significant changes with a lot more risk.
I've put the things I didn't take into
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=rpurdie/dizzy-next just so we can discuss them. We also need the other changes fror the buildtools change, those should go in together, I believe you already talked with Paul about that. We did manage a fairly green build on the autobuilder recently.
As you mentioned, we do need to sort out which changes make sense for
linux-yocto, I'm hoping Bruce can help advise on that. We may be cutting
things tight to have a build this weekend if we don't have those (so QA
could look at this next week).
Cheers,
Richard
next prev parent reply other threads:[~2014-12-31 10:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 17:10 [PATCH 0/3] Dizzy next Dec 15th V2 Armin Kuster
2014-12-15 17:10 ` [PATCH 1/3] cpio: fix bug CVE-2014-9112 for cpio-2.8 Armin Kuster
2014-12-15 17:10 ` [PATCH 2/3] cpio: fix bug CVE-2014-9112 for cpio-2.11 Armin Kuster
2014-12-15 17:10 ` [PATCH 3/3] python: fix ssl import error Armin Kuster
2014-12-31 10:26 ` Richard Purdie [this message]
2015-01-03 0:41 ` Dizzy Merging akuster808
2015-01-06 14:01 ` Paul Eggleton
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=1420021585.25779.14.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