From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Paul Eggleton <bluelightning@bluelightning.org>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH 7/9] release-notes: Add CVEs, recipe upgrades and contributors for 5.0
Date: Thu, 18 Apr 2024 17:26:06 +0200 [thread overview]
Message-ID: <3233e285-4879-40f5-970e-995652ea8468@bootlin.com> (raw)
In-Reply-To: <5f8f7c584f188422ac0fa7ba56a588b4@bluelightning.org>
Hi Paul,
On 4/18/24 at 16:47, Paul Eggleton wrote:
>
>>
>> I had to replace :cve:`2023-6237 by :cve_mitre:`2023-6237` as this
>> was a "reserved" CVE.
>
> Thanks for checking these. I wonder if we can do this in an automated
> way (or do you have something that you use already?)
Maybe, but so far I'm using a manual way. That's slooow... :-/
>
>>> Contributors to 5.0
>>> ~~~~~~~~~~~~~~~~~~~
>>> Thanks to the following people who contributed to this release:
>>> ...
>>> +- Arne Schwerdt
>>> +- Bartosz Golaszewski
>>> +- Baruch Siach
>>> +- baruch@tkos.co.il
>>
>> Removed that last line as this is the same person :)
>
>
>>
>> Cheers
>> Paul
> Well spotted! I'm usually pretty good at finding those but somehow
> even after looking backwards and forwards I over the list I missed it.
Same for me, I'm only good at finding other people's mistakes, but not
mine :)
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2024-04-18 15:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-14 20:43 [PATCH 0/9] Updates for the 5.0 release Paul Eggleton
2024-04-14 20:43 ` [PATCH 1/9] ref-manual: Add virtual-slash QA check Paul Eggleton
2024-04-14 20:43 ` [PATCH 2/9] ref-manual: add new python classes Paul Eggleton
2024-04-15 13:43 ` Michael Opdenacker
2024-04-14 20:43 ` [PATCH 3/9] classes: cve_check: add note about remote patches Paul Eggleton
2024-04-14 20:43 ` [PATCH 4/9] variables: add TARGET_DBGSRC_DIR Paul Eggleton
2024-04-14 20:43 ` [PATCH 5/9] dev-manual: update reference to sstate-cache-management script Paul Eggleton
2024-04-14 20:43 ` [PATCH 6/9] dev-manual: update custom distribution section Paul Eggleton
2024-04-15 14:04 ` Michael Opdenacker
2024-04-14 20:43 ` [PATCH 7/9] release-notes: Add CVEs, recipe upgrades and contributors for 5.0 Paul Eggleton
2024-04-15 14:24 ` Michael Opdenacker
2024-04-18 14:47 ` [docs] " Paul Eggleton
2024-04-18 15:26 ` Michael Opdenacker [this message]
2024-04-14 20:43 ` [PATCH 8/9] migration: Extend migration guide " Paul Eggleton
2024-04-15 14:41 ` Michael Opdenacker
2024-04-14 20:43 ` [PATCH 9/9] release-notes: additional features and one known issue " Paul Eggleton
2024-04-15 8:06 ` [docs] " Quentin Schulz
2024-04-15 15:22 ` Michael Opdenacker
2024-04-18 14:50 ` Paul Eggleton
2024-04-15 15:41 ` Michael Opdenacker
2024-04-15 15:43 ` [PATCH 0/9] Updates for the 5.0 release 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=3233e285-4879-40f5-970e-995652ea8468@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=bluelightning@bluelightning.org \
--cc=docs@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