From: "Usman, Fahad" <Fahad_Usman@mentor.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: Christopher Larson <chris_larson@mentor.com>,
openembedded-devel@lists.openembedded.org
Subject: Re: [meta-networking][dylan][PATCH] libmtp: add new recipe
Date: Wed, 12 Jun 2013 15:37:25 +0500 [thread overview]
Message-ID: <51B84F65.7010301@mentor.com> (raw)
In-Reply-To: <3639423.KAoAmRbK6q@helios>
On 06/12/2013 02:45 PM, Paul Eggleton wrote:
> It looks like this recipe is not in master so it would need to go there first.
> I'm also not sure if this is really suitable for meta-networking; MTP is
> indeed a protocol but it's more something for communicating with cameras and
> media players, so I'd suggest the meta-oe layer for this where we have other
> similar components (gphoto2, libimobiledevice, etc...)
>
> Cheers,
> Paul
Hi Paul,
I will re-submit this patch against master branch and in
meta-oe/recipes-connectivity
Thanks,
Fahad.
prev parent reply other threads:[~2013-06-12 10:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 7:08 [meta-networking][dylan][PATCH] libmtp: add new recipe Fahad Usman
2013-06-12 9:45 ` Paul Eggleton
2013-06-12 10:37 ` Usman, Fahad [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=51B84F65.7010301@mentor.com \
--to=fahad_usman@mentor.com \
--cc=chris_larson@mentor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.