From: akuster808 <akuster808@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [RFC] remove neon from oe-core
Date: Tue, 09 Jun 2015 18:41:05 -0700 [thread overview]
Message-ID: <557795B1.6020304@gmail.com> (raw)
In-Reply-To: <CAJTo0LY2C3d6ewKs7f1V0U9k7vqMQ47kCnANetzGz1OhMtfTFg@mail.gmail.com>
Sounds good to me.
- armin
On 06/09/2015 12:14 PM, Burton, Ross wrote:
> Hi,
>
> Since Subversion moved away from neon it appears the only user of it in
> oe-core is GStreamer as a HTTP client plugin. By virtue of being
> maintained I suspect the libsoup plugin is generally the better choice
> there, so as neon is now unmaintained upstream (last release September
> 2014, doesn't work with latest GnuTLS release) I propose moving it to
> meta-oe.
>
> Any comments?
>
> Ross
>
>
next prev parent reply other threads:[~2015-06-10 1:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 19:14 [RFC] remove neon from oe-core Burton, Ross
2015-06-10 1:41 ` akuster808 [this message]
2015-06-10 9:17 ` Paul Eggleton
2015-06-10 9:31 ` Burton, Ross
2015-06-10 10:03 ` Martin Jansa
2015-06-10 10:24 ` Burton, Ross
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=557795B1.6020304@gmail.com \
--to=akuster808@gmail.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