From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>,
Joshua Lock <joshuagloe@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/9] Proposed changes for fido
Date: Fri, 15 Jan 2016 13:15:16 +0000 [thread overview]
Message-ID: <1452863716.28375.162.camel@linuxfoundation.org> (raw)
In-Reply-To: <20160115121053.GB2607@jama>
On Fri, 2016-01-15 at 13:10 +0100, Martin Jansa wrote:
> On Wed, Dec 23, 2015 at 01:40:36PM +0000, Joshua Lock wrote:
> > From: Joshua Lock <joshua.lock@collabora.co.uk>
> >
> > Please consider the following fixes, available in the joshuagl/fido
> > -next
> > branch of openembedded-core-contrib, for the fido branch.
>
> When is this going to be merged?
Its done, sorry about the delay. I'm aiming to do better with these...
Cheers,
Richard
prev parent reply other threads:[~2016-01-15 13:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 13:40 [PATCH 0/9] Proposed changes for fido Joshua Lock
2016-01-15 12:10 ` Martin Jansa
2016-01-15 13:15 ` Richard Purdie [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=1452863716.28375.162.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=joshuagloe@gmail.com \
--cc=martin.jansa@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