Openembedded Core Discussions
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	 "joshua.lock" <joshua.lock@collabora.co.uk>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Fido and dizzy collaboration?
Date: Fri, 04 Sep 2015 16:51:33 -0700	[thread overview]
Message-ID: <55EA2E85.8020700@gmail.com> (raw)
In-Reply-To: <1441139962.24871.16.camel@linuxfoundation.org>



On 09/01/2015 01:39 PM, Richard Purdie wrote:
> Hi Armin, Joshua,
> 
> I've just been looking at the patches queued for the dizzy/fido
> branches. In fact I ended up merging them before I realised there are
> some issues.
> 
> The problem is there are dizzy patches which aren't in fido, which
> breaks our policies. 

I thought the changes had to be in Master first. Are you saying I need
to wait for them to be in fido first?

Could the two of you work to resolve that and give
> me fido branch to pull which resolved it please?

Will do.

- armin
> 
> I didn't take the dizzy patch related to S = ${WORKDIR} since that
> looked more like a change appropriate to master only. The bitbake
> patches also need handling on the bitbake list if we really do want to
> backport them to 1.26 and 1.24.
> 
> Cheers,
> 
> Richard
> 


      parent reply	other threads:[~2015-09-04 23:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-01 20:39 Fido and dizzy collaboration? Richard Purdie
2015-09-02  9:47 ` Joshua Lock
2015-09-02 17:10 ` Joshua Lock
2015-09-04 23:51 ` akuster808 [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=55EA2E85.8020700@gmail.com \
    --to=akuster808@gmail.com \
    --cc=joshua.lock@collabora.co.uk \
    --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