From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: OpenEmbedded Devel List
<openembedded-devel@lists.openembedded.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [oe] qt4 moves out of oe-core - to meta-qt4, or to meta-oe?
Date: Mon, 16 Nov 2015 13:23:37 +0200 [thread overview]
Message-ID: <5649BCB9.4090708@linux.intel.com> (raw)
In-Reply-To: <CAP9ODKpU_6sVy6iidiCem8Sb+EWAgNCVrvOPmOhr4_uMt174Hw@mail.gmail.com>
On 11/16/2015 01:20 PM, Otavio Salvador wrote:
>> Making a separate repository with this layer is even more disruptive, and
>> complicates administration and maintenance. I'm not going to handle those.
>> So I'll make a meta-qt4 layer under meta-oe, and it's fine if there is no
>> official maintainer or ongoing build testing for it at least until someone
>> volunteers to pick it up.
>
> I will nack the patch to include it onto meta-oe; I also guess that
> Martin will also nack it.
>
> Make it another layer as suggested, please.
A separate layer under meta-openembedded or a separate repository with
the layer? Please be clear.
Alex
next prev parent reply other threads:[~2015-11-16 11:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 16:45 qt4 moves out of oe-core - to meta-qt4, or to meta-oe? alexander.kanavin
2015-11-12 17:03 ` Andreas Müller
2015-11-12 19:08 ` Paul Eggleton
2015-11-13 11:39 ` [oe] " Otavio Salvador
2015-11-13 11:46 ` Martin Jansa
2015-11-16 9:43 ` Alexander Kanavin
2015-11-16 10:07 ` Andreas Oberritter
2015-11-16 10:26 ` volunteers for meta-qt4 repo maintenance? Alexander Kanavin
2015-11-18 22:08 ` Paul Eggleton
2015-11-16 11:20 ` [oe] qt4 moves out of oe-core - to meta-qt4, or to meta-oe? Otavio Salvador
2015-11-16 11:23 ` Alexander Kanavin [this message]
2015-11-16 11:24 ` Otavio Salvador
2015-11-16 17:10 ` akuster808
2015-11-16 17:39 ` Mark Hatle
2015-11-12 17:19 ` Martin Jansa
2015-11-12 17:38 ` alexander.kanavin
2015-11-12 18:59 ` Martin Jansa
2015-11-16 10:37 ` [oe] " 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=5649BCB9.4090708@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
/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