From: Oleg Zhurakivskyy <oleg.zhurakivskyy@intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2] Add libedit, neardal recipes
Date: Thu, 19 Feb 2015 13:24:00 +0200 [thread overview]
Message-ID: <54E5C7D0.70603@intel.com> (raw)
In-Reply-To: <CAJTo0Lb_fpZ5iahemsp7BX9en+AA6Q9rtnzT0-_6omWkvvVZ+g@mail.gmail.com>
Hi Ross,
On 02/19/2015 01:00 PM, Burton, Ross wrote:
>> Just to make sure I understood correctly regarding meta-connectivity, is that meta-oe/recipes-connectivity?
>
> Sorry, typos abound. Yes, meta-oe/recipes-connectivity.
OK. Thanks a lot!
Regards,
Oleg
prev parent reply other threads:[~2015-02-19 11:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 13:01 [PATCH 0/2] Add libedit, neardal recipes Oleg Zhurakivskyy
2015-02-12 13:01 ` [PATCH 1/2] libedit: Add recipe Oleg Zhurakivskyy
2015-02-12 13:01 ` [PATCH 2/2] neardal: " Oleg Zhurakivskyy
2015-02-13 16:53 ` [PATCH 0/2] Add libedit, neardal recipes Burton, Ross
2015-02-16 9:09 ` Oleg Zhurakivskyy
2015-02-19 11:00 ` Burton, Ross
2015-02-19 11:24 ` Oleg Zhurakivskyy [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=54E5C7D0.70603@intel.com \
--to=oleg.zhurakivskyy@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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