From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Cliff Brake <cbrake@bec-systems.com>,
Paul Eggleton <paul.eggleton@linux.intel.com>
Subject: Re: [meta-oe][PATCH 1/6] libraw1394: add recipe
Date: Mon, 14 Oct 2013 14:11:33 +0200 [thread overview]
Message-ID: <20131014121133.GB3708@jama> (raw)
In-Reply-To: <1D7F89CC-74A8-4960-BE17-B59701B0F943@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]
On Sun, Oct 13, 2013 at 12:45:38PM -0700, Khem Raj wrote:
>
> On Oct 13, 2013, at 4:10 AM, Paul Eggleton <paul.eggleton@linux.intel.com> wrote:
>
> > On Sunday 13 October 2013 01:43:50 Khem Raj wrote:
> >> From: Cliff Brake <cbrake@bec-systems.com>
> >>
> >> Initial recipe created by Khem Raj
> >>
> >> Signed-off-by: Cliff Brake <cbrake@bec-systems.com>
> >> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> >> ---
> >> meta-oe/recipes-multimedia/libraw1394/libraw1394_2.0.9.bb | 11 +++++++++++
> >
> > Could these multimedia recipes go into meta-multimedia instead of meta-oe?
>
> Its ok to put them into meta-multimedia, but they depend on meta-oe a lot
> may be more recipes like opencv should be moved as well.
>
> Martin, do you need a fresh set of patches for it or can you handle the move from
> meta-oe -> meta-multimedia
If you're going to move opencv as well, then please send new fresh set
of patches. Thanks.
>
> >
> > Cheers,
> > Paul
> >
> > --
> >
> > Paul Eggleton
> > Intel Open Source Technology Centre
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-10-14 12:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-13 8:43 [meta-oe][PATCH 1/6] libraw1394: add recipe Khem Raj
2013-10-13 8:43 ` [meta-oe][PATCH 2/6] libdc1394: " Khem Raj
2013-10-13 8:43 ` [meta-oe][PATCH 3/6] coriander: " Khem Raj
2013-10-13 8:43 ` [meta-oe][PATCH 4/6] libmikmod: Upgrade libmikmod_3.2.0.bb -> libmikmod_3.3.2.bb Khem Raj
2013-10-16 0:47 ` Martin Jansa
2013-10-16 4:20 ` Khem Raj
2013-10-13 8:43 ` [meta-oe][PATCH 5/6] opencv: Upgrade to latest on 2.4 branch Khem Raj
2013-10-13 8:43 ` [meta-gnome][PATCH 6/6] libgnomeui: Depend on libgnome-keyring not gnome-keyring Khem Raj
2013-10-13 11:10 ` [meta-oe][PATCH 1/6] libraw1394: add recipe Paul Eggleton
2013-10-13 19:45 ` Khem Raj
2013-10-14 12:11 ` Martin Jansa [this message]
2013-10-14 12:48 ` Koen Kooi
2013-10-14 12:56 ` Paul Eggleton
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=20131014121133.GB3708@jama \
--to=martin.jansa@gmail.com \
--cc=cbrake@bec-systems.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paul.eggleton@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