From: Joshua Lock <joshua.lock@collabora.co.uk>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
Armin Kuster <akuster808@gmail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Fido and dizzy collaboration?
Date: Wed, 02 Sep 2015 10:47:54 +0100 [thread overview]
Message-ID: <1441187274.3128.6.camel@collabora.co.uk> (raw)
In-Reply-To: <1441139962.24871.16.camel@linuxfoundation.org>
On Tue, 2015-09-01 at 21:39 +0100, 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. Could the two of you work to resolve that and
> give
> me fido branch to pull which resolved it please?
Sure, I'll start working on this today.
Regards,
Joshua
next prev parent reply other threads:[~2015-09-02 9:47 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 [this message]
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=1441187274.3128.6.camel@collabora.co.uk \
--to=joshua.lock@collabora.co.uk \
--cc=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