From: Khem Raj <raj.khem@gmail.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Remove pth recipe
Date: Wed, 13 Jan 2016 09:36:44 -0800 [thread overview]
Message-ID: <2EB9392C-58FE-4807-9E1D-41738D761079@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 422 bytes --]
Hi All,
We are carrying pth recipe in OE-Core.
1. There are no packages in OE-Core which depend on it.
2. pth is quite old ( last release was in 2006) moreover there is npth replacement available and we have recipe in OE-Core
I would like to propose a removal of this recipe but before doing so,
but wanted to find if there are any active users of this package
if you use it the please respond
-Khem
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]
next reply other threads:[~2016-01-13 17:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 17:36 Khem Raj [this message]
2016-01-15 18:18 ` Remove pth recipe Richard Purdie
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=2EB9392C-58FE-4807-9E1D-41738D761079@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
/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