From: "Takayasu Ito" <ito@lineo.co.jp>
To: poky@lists.yoctoproject.org
Cc: docs@lists.yoctoproject.org
Subject: yocto-3.1.22/RELEASENOTES
Date: Mon, 23 Jan 2023 17:55:49 +0900 [thread overview]
Message-ID: <8ada8dc6-fb4b-5042-9fce-d0926d422226@lineo.co.jp> (raw)
I was checking the following RELEASENOTE contents, and the CVE for
cairo vulnerability has already been fixed in 2019 and the change in the
PATCH file is that the status of the upstream PATCH has been changed
from pending to backported.
http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.22/RELEASENOTES
--
Takayasu Ito
Yocto Project Ambassador
Solution Department Lineo Solutions, Inc.
https://www.lineo.co.jp/english/
Email: ito@lineo.co.jp
next reply other threads:[~2023-01-23 8:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 8:55 Takayasu Ito [this message]
2023-01-25 15:10 ` [docs] yocto-3.1.22/RELEASENOTES Richard Purdie
2023-01-26 0:14 ` [poky] " Takayasu Ito
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=8ada8dc6-fb4b-5042-9fce-d0926d422226@lineo.co.jp \
--to=ito@lineo.co.jp \
--cc=docs@lists.yoctoproject.org \
--cc=poky@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).