From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/5] recipes-lsb4/perl: remove the recipes
Date: Thu, 04 May 2017 11:49:38 +0100 [thread overview]
Message-ID: <1493894978.23535.113.camel@linuxfoundation.org> (raw)
In-Reply-To: <20170503131153.1780-4-alexander.kanavin@linux.intel.com>
On Wed, 2017-05-03 at 16:11 +0300, Alexander Kanavin wrote:
> These were required by LSB 4.1 tests; there's no other reason to
> continue
> carrying them in oe-core.
We did discuss LSB and agreed we'd document which pieces we'd support
and not support. Can we add such a text file before we start deleting
things please?
[I'm totally in favour of killing off some of these things, but we need
to do what we said we'd do]
Cheers,
Richard
next prev parent reply other threads:[~2017-05-04 10:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 13:11 [PATCH 1/5] liberation-fonts: update to 2.00.1 Alexander Kanavin
2017-05-03 13:11 ` [PATCH 2/5] packagegroup-core-lsb: do not include Qt4 anymore Alexander Kanavin
2017-05-03 13:11 ` [PATCH 3/5] libpng12: remove the recipe Alexander Kanavin
2017-05-03 18:41 ` Max Krummenacher
2017-05-03 18:58 ` Burton, Ross
2017-05-04 9:18 ` Alexander Kanavin
2017-05-04 9:54 ` Burton, Ross
2017-05-04 23:48 ` Max Krummenacher
2017-05-05 9:16 ` Alexander Kanavin
2017-05-07 23:46 ` Paul Eggleton
2017-05-05 10:10 ` Burton, Ross
2017-05-03 13:11 ` [PATCH 4/5] recipes-lsb4/perl: remove the recipes Alexander Kanavin
2017-05-04 10:49 ` Richard Purdie [this message]
2017-05-04 10:54 ` Alexander Kanavin
2017-05-04 11:16 ` Richard Purdie
2017-05-03 13:11 ` [PATCH 5/5] mailx: remove the recipe Alexander Kanavin
2017-05-03 13:31 ` ✗ patchtest: failure for "liberation-fonts: update to 2...." and 4 more Patchwork
2017-05-03 21:43 ` Paul Eggleton
2017-05-04 9:33 ` Alexander Kanavin
2017-05-04 10:07 ` Paul Eggleton
2017-05-04 10:16 ` Alexander Kanavin
2017-05-04 10:32 ` Peter Kjellerstedt
2017-05-04 10:32 ` Paul Eggleton
2017-05-04 15:36 ` Leonardo Sandoval
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=1493894978.23535.113.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@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