From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] libao: add version 1.1.0
Date: Tue, 15 Oct 2013 09:57:44 +0100 [thread overview]
Message-ID: <4294043.nodQZTOtl3@helios> (raw)
In-Reply-To: <525C309F.8080306@linux.intel.com>
On Monday 14 October 2013 10:57:51 Saul Wold wrote:
> On 09/17/2013 07:49 AM, JC wrote:
> > This is basically a 99% import of Peter Tworek's recipe from
> > tworaz666@gmail.com found in
> > https://github.com/tworaz/oe-tworaz/blob/master/meta-jlime/recipes-suppor
> > t/libao/libao_1.1.0.bb
>
> Can you give some details as to why we should included it in core vs
> meta-oe?
It was sent to the wrong list; Jay re-sent it to the openembedded-devel list
and it has already been merged into meta-multimedia.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2013-10-15 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 14:49 [PATCH] libao: add version 1.1.0 JC
2013-10-14 17:57 ` Saul Wold
2013-10-15 8:57 ` Paul Eggleton [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=4294043.nodQZTOtl3@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.com \
/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