From: Christian Gagneraud <chgans@gna.org>
To: yocto@yoctoproject.org
Subject: Re: Yocto Project 1.5_M5.rc6
Date: Fri, 11 Oct 2013 14:56:37 +1300 [thread overview]
Message-ID: <52575AD5.8000002@gna.org> (raw)
In-Reply-To: <52575854.6080302@linux.intel.com>
On 11/10/13 14:45, Saul Wold wrote:
>
> Sorry for the top post here. The real reason we still have Qt3 is
> because it's required part of the LSB spec. OE-Core contains Qt4 and we
> know that meta-qt5 exists from Otavio and Martin.
Thanks for the explanation.
>
> I know that Richard and Paul have been watching what's going on with
> meta-qt5.
Good to hear.
Chris
>
> Sau!
>
> On 10/10/2013 05:31 PM, Jeff Osier-Mixon wrote:
>> Game, set, and match! This is also why I don't play golf!
>>
>> There are many layers I would love to see in the YP QA process and I
>> would count meta-qt5 in the top priority. However, we only have so
>> many resources, so we have to focus on the core right now. I'd be
>> happy to talk offline about finding ways to locate new resources.
>>
>> On Thu, Oct 10, 2013 at 5:01 PM, Otavio Salvador
>> <otavio@ossystems.com.br> wrote:
>>> On Thu, Oct 10, 2013 at 7:26 PM, Christian Gagneraud <chgans@gna.org>
>>> wrote:
>>>> On 11/10/13 11:02, Jeff Osier-Mixon wrote:
>>>>>
>>>>> Hi Chris - well-intended sarcasm isn't usually a problem, but I want
>>>>> to make sure to address your concerns here. We would like to see a
>>>>> meta-qt5 as well but so far one has not been submitted. If you would
>>>>> like to submit one, I would be happy to put you in touch with the
>>>>> right maintainers who can guide you through the process.
>>>>
>>>>
>>>> Hi Jeff,
>>>>
>>>> Well-intended answer! ;) But i want to make sure to address your
>>>> concerns
>>>> here. I would like to see the meta-qt5 [1] in Yocto's QA process. If
>>>> you
>>>> would like to integrate it, I would be happy to put you in touch
>>>> with the
>>>> right maintainers who can guide you through the process.
>>>>
>>>> Chris.
>>>>
>>>> [1] https://github.com/meta-qt5
>>>
>>> Hey, this was even easier.
>>>
>>> I am one of meta-qt5 maintainers and I am sure Martin will be more
>>> than happy to get it into the QA process. Jeff ... this was easy :-)
>>>
>>> --
>>> Otavio Salvador O.S. Systems
>>> http://www.ossystems.com.br http://code.ossystems.com.br
>>> Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
>>
>>
>>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
prev parent reply other threads:[~2013-10-11 1:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 22:35 Yocto Project 1.5_M5.rc6 Flanagan, Elizabeth
2013-10-10 21:37 ` Christian Gagneraud
2013-10-10 22:02 ` Jeff Osier-Mixon
2013-10-10 22:26 ` Christian Gagneraud
2013-10-11 0:01 ` Otavio Salvador
2013-10-11 0:31 ` Jeff Osier-Mixon
2013-10-11 1:45 ` Saul Wold
2013-10-11 1:55 ` Otavio Salvador
2013-10-11 2:08 ` Christian Gagneraud
2013-10-14 15:36 ` Georgescu, Alexandru C
2013-10-11 1:56 ` Christian Gagneraud [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=52575AD5.8000002@gna.org \
--to=chgans@gna.org \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.