From: "Takayasu Ito" <ito@lineo.co.jp>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
poky@lists.yoctoproject.org
Cc: docs@lists.yoctoproject.org
Subject: Re: [poky] [docs] yocto-3.1.22/RELEASENOTES
Date: Thu, 26 Jan 2023 09:14:04 +0900 [thread overview]
Message-ID: <f6e45090-3a66-a066-7b89-f59a7c2b504f@lineo.co.jp> (raw)
In-Reply-To: <1003421ce4ffd0b93c7dabe3b2aa7c0b5c240746.camel@linuxfoundation.org>
Considering that the Security Fixes section lists CVEs whose status has
been changed to fixed by this release, I think it is appropriate that
this update to the cairo patch file be listed under Fixes.
On 2023/01/26 0:10, Richard Purdie wrote:
> On Mon, 2023-01-23 at 17:55 +0900, Takayasu Ito wrote:
>> 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
>>
>
> The patch was updated in:
>
> https://git.yoctoproject.org/poky/commit/?h=dunfell&id=6e97ceb8586281a8d594a3a1ab9e303fd34e1d4a
>
> which seems to match the change log and release notes? It wasn't just
> the patch status but the patch itself as well?
>
> Cheers,
>
> Richard
>
>
>
>
>
--
Takayasu Ito
Yocto Project Ambassador
Solution Department Lineo Solutions, Inc.
https://www.lineo.co.jp/english/
Email: ito@lineo.co.jp
prev parent reply other threads:[~2023-01-26 0:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 8:55 yocto-3.1.22/RELEASENOTES Takayasu Ito
2023-01-25 15:10 ` [docs] yocto-3.1.22/RELEASENOTES Richard Purdie
2023-01-26 0:14 ` Takayasu Ito [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=f6e45090-3a66-a066-7b89-f59a7c2b504f@lineo.co.jp \
--to=ito@lineo.co.jp \
--cc=docs@lists.yoctoproject.org \
--cc=poky@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 read-only IMAP folder(s) and NNTP newsgroup(s).