From: Patrick Ohly <patrick.ohly@intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH 1/2] libgphoto2: fix compatibility with libjpeg-turbo
Date: Thu, 16 Jun 2016 11:09:04 +0200 [thread overview]
Message-ID: <1466068144.19334.34.camel@intel.com> (raw)
In-Reply-To: <1466003282-21411-1-git-send-email-patrick.ohly@intel.com>
On Wed, 2016-06-15 at 17:08 +0200, Patrick Ohly wrote:
> +Upstream-Status: Submitted [https://github.com/gphoto/libgphoto2/pull/64]
FWIW, the patch was merged, so "Backported" is now more accurate.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2016-06-16 9:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 10:45 State of bitbake world 2016-06-13 Martin Jansa
[not found] ` <1466002419.9543.1.camel@intel.com>
2016-06-15 15:08 ` [meta-oe][PATCH 1/2] libgphoto2: fix compatibility with libjpeg-turbo Patrick Ohly
2016-06-15 15:08 ` [meta-oe][PATCH 2/2] v4l-utils: " Patrick Ohly
2016-06-16 9:09 ` Patrick Ohly [this message]
2016-06-15 15:29 ` [OE-core] State of bitbake world 2016-06-13 Martin Jansa
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=1466068144.19334.34.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=openembedded-devel@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