From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: mail@nico-maas.de, toaster@lists.yoctoproject.org
Subject: Re: [Toaster] Toaster failing
Date: Tue, 05 Apr 2022 20:40:39 +0100 [thread overview]
Message-ID: <f260eabbb6affdf9fa8aa53097d4c94cdd1b16fb.camel@linuxfoundation.org> (raw)
In-Reply-To: <30045.1649145109879927494@lists.yoctoproject.org>
On Tue, 2022-04-05 at 00:51 -0700, mail via lists.yoctoproject.org wrote:
> I tried this with the master branch and it seems like its working.
Great, thanks for testing.
> Some questions:
> 1.) When is Kirkstone planned for release?
We're about to make a release candidate build and the final release would ship
in around 1-3 weeks after that depending on how things go.
> 2.) Are these bugfixes backported to Honister and Hardknott?
They weren't but a few of us talked about this today and they are merged back to
those branches now so things might hopefully work better there.
Cheers,
Richard
next prev parent reply other threads:[~2022-04-05 19:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3ee004b6c31c97b9918bc03d2f702229cd74ab7a.camel@linuxfoundation.org>
2022-04-05 7:51 ` Toaster failing mail
2022-04-05 19:40 ` Richard Purdie [this message]
2022-04-05 20:23 ` [Toaster] " Tim Orling
2022-04-06 6:28 ` mail
2022-04-07 11:03 ` mail
2022-04-27 6:07 ` mail
2022-04-27 6:55 ` mail
2022-04-29 12:20 ` mail
2022-05-01 21:12 ` [Toaster] " Reyna, David
2022-05-01 21:16 ` Reyna, David
2022-05-01 21:18 ` Reyna, David
2022-05-02 16:12 ` mail
2022-05-04 10:02 ` [Toaster] " Reyna, David
2022-05-04 10:28 ` mail
2022-05-11 12:21 ` mail
2022-05-11 16:59 ` [Toaster] " Reyna, David
2022-05-12 7:57 ` mail
2022-06-02 10:49 ` mail
2022-06-06 8:13 ` [Toaster] " Reyna, David
2022-06-10 7:05 ` Reyna, David
2022-06-10 7:09 ` mail
2022-08-01 10:17 ` mail
2022-11-09 6:03 ` mail
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=f260eabbb6affdf9fa8aa53097d4c94cdd1b16fb.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=mail@nico-maas.de \
--cc=toaster@lists.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.