Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Armin Kuster <akuster808@gmail.com>,
	"joshua.lock" <joshua.lock@collabora.co.uk>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Fido and dizzy collaboration?
Date: Tue, 01 Sep 2015 21:39:22 +0100	[thread overview]
Message-ID: <1441139962.24871.16.camel@linuxfoundation.org> (raw)

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. Could the two of you work to resolve that and give
me fido branch to pull which resolved it please?

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



             reply	other threads:[~2015-09-01 20:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-01 20:39 Richard Purdie [this message]
2015-09-02  9:47 ` Fido and dizzy collaboration? Joshua Lock
2015-09-02 17:10 ` Joshua Lock
2015-09-04 23:51 ` akuster808

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=1441139962.24871.16.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=akuster808@gmail.com \
    --cc=joshua.lock@collabora.co.uk \
    --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