From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
Lee Chee Yang <chee.yang.lee@intel.com>
Cc: YP docs mailing list <docs@lists.yoctoproject.org>
Subject: Re: [docs] [yocto] [ANNOUNCEMENT] Yocto Project 4.0 is Released
Date: Wed, 27 Apr 2022 09:52:23 +0200 [thread overview]
Message-ID: <e9fa06f7-e9a0-3357-dfc4-e8b9611a88a7@bootlin.com> (raw)
In-Reply-To: <02ba4e468b4f2438a8ed6d59e824a0ffcc8ab619.camel@linuxfoundation.org>
On 4/27/22 09:51, Richard Purdie wrote:
> On Wed, 2022-04-27 at 09:41 +0200, Michael Opdenacker via lists.yoctoproject.org
> wrote:
>> Thanks for the great news!
>> Shouldn't we highlight in the documentation
>> (https://docs.yoctoproject.org/migration-guides/migration-4.0.html#release-notes-for-4-0-kirkstone)
>> that this is our new Long Term Support release?
>>
>> This would help to spread the news.
> Please. Perhaps you could help us there? :)
Sure, I'll post a patch :)
Thanks
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2022-04-27 7:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DM5PR1101MB236176E376BD554365050E72B9FA9@DM5PR1101MB2361.namprd11.prod.outlook.com>
[not found] ` <9d339a31-a732-3de3-53ee-45a1054d5c92@bootlin.com>
2022-04-27 7:51 ` [docs] [yocto] [ANNOUNCEMENT] Yocto Project 4.0 is Released Richard Purdie
2022-04-27 7:52 ` Michael Opdenacker [this message]
[not found] ` <90b05148-5215-584e-0080-24cd411b2ba8@sancloud.com>
[not found] ` <CANPvuR=Sp+tuOAmFRzw207e_1+jNzOyR1AST9J=jh7_KgsOS2Q@mail.gmail.com>
[not found] ` <9790963d-0e8d-c713-cc97-ab6f8ca4fef3@bootlin.com>
2022-04-27 11:17 ` Nicolas Dechesne
2022-04-27 11:27 ` Nicolas Dechesne
2022-04-27 11:56 ` Nicolas Dechesne
2022-04-27 12:32 ` Michael Opdenacker
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=e9fa06f7-e9a0-3357-dfc4-e8b9611a88a7@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=chee.yang.lee@intel.com \
--cc=docs@lists.yoctoproject.org \
--cc=richard.purdie@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).