Openembedded Core Discussions
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Dizzy Merging
Date: Fri, 02 Jan 2015 16:41:01 -0800	[thread overview]
Message-ID: <54A73A9D.8080903@gmail.com> (raw)
In-Reply-To: <1420021585.25779.14.camel@linuxfoundation.org>



On 12/31/2014 02:26 AM, Richard Purdie wrote:
> 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.
>
ok.
> 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.

no worries.

>
> 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.
>

I thought I included one of the two commits in my contrib branch.

http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=akuster/dizzy_1_7_1&id=e8a6adf0612fc6d9ca703237a3a5c630177c2f34

Am I pulling over the missing commit or are you going to pull them over 
from Paul's request.

"The following changes since commit 
1cf1edcd28a002291622d04dd2d0ee2c67e329e4:

   buildtools-tarball: package all of Python (2014-12-11 16:34:01 +0000)

are available in the git repository at:

   git://git.openembedded.org/openembedded-core-contrib 
paule/dizzy-git-tools
 
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/dizzy-git-tools

Jackie Huang (1):
   packagegroup-self-hosted: add git-perltools

Paul Eggleton (1):
   buildtools-tarball: restore missing git tools
"

> 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).

K.

Thanks,
Armin
>
> Cheers,
>
> Richard
>


  reply	other threads:[~2015-01-03  0:41 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 ` Dizzy Merging Richard Purdie
2015-01-03  0:41   ` akuster808 [this message]
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=54A73A9D.8080903@gmail.com \
    --to=akuster808@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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