From: akuster808 <akuster808@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
Paul Eggleton <paul.eggleton@linux.intel.com>,
yocto@yoctoproject.org
Subject: Re: Yocto layers missing thud branches
Date: Tue, 20 Nov 2018 16:21:34 -0700 [thread overview]
Message-ID: <6e014304-0816-d141-2e9e-4e5ca168eba6@gmail.com> (raw)
In-Reply-To: <9139d99908dae9aa03be1ae5cf07720206c9755c.camel@linuxfoundation.org>
On 11/20/18 4:05 PM, Richard Purdie wrote:
> On Mon, 2018-11-19 at 09:47 +1300, Paul Eggleton wrote:
>> On Monday, 19 November 2018 12:11:35 AM NZDT Max Krummenacher wrote:
>>> Am Samstag, den 17.11.2018, 15:50 -0800 schrieb akuster808:
>>>> Can the maintainers of meta-qt3, meta-qt4, meta-selinux, and
>>>> meta-cgl
>>>> please add a "Thud" branch
>>>>
>>> While at it, the following patches declaring thud compatibility are
>>> not
>>> yet applied:
>>>
> https://lists.yoctoproject.org/pipermail/yocto/2018-October/042780.html
> https://lists.yoctoproject.org/pipermail/yocto/2018-October/042922.html
> https://lists.yoctoproject.org/pipermail/yocto/2018-October/042923.html
>> I have just taken care of meta-qt3 and meta-qt4, FWIW.
> Given we don't test those any more, should we be pushing these new
> branches?
Are the branching schemes in sync with what we test , build or both? I
think we should be clear what is built or built and tested if there are
exception.
The 2.6 release notes called out so it may lead to the conclusion its
tested.
Release Name: meta-qt3-thud-20.0.0
Branch: thud
Tag: thud-20.0.0
Hash: 02f273cba6c25f5cf20cb66d8a417a83772c3179
md5: 7b73bf1132428ea898938b03815cad21
- armin
>
> Cheers,
>
> Richard
>
next prev parent reply other threads:[~2018-11-20 23:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-17 23:50 Yocto layers missing thud branches akuster808
2018-11-17 23:53 ` Nicolas Dechesne
2018-11-18 11:11 ` Max Krummenacher
2018-11-18 20:47 ` Paul Eggleton
2018-11-18 21:11 ` akuster808
2018-11-20 23:05 ` Richard Purdie
2018-11-20 23:21 ` akuster808 [this message]
2018-11-20 23:55 ` richard.purdie
2018-11-22 15:10 ` Matthias Schoepfer
2018-11-22 16:42 ` Stephen Lawrence
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=6e014304-0816-d141-2e9e-4e5ca168eba6@gmail.com \
--to=akuster808@gmail.com \
--cc=paul.eggleton@linux.intel.com \
--cc=richard.purdie@linuxfoundation.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.