From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Paul Eggleton <bluelightning@bluelightning.org>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH 06/12] release-notes-4.3: add CVEs, recipe upgrades, license changes, contributors
Date: Mon, 6 Nov 2023 18:07:41 +0100 [thread overview]
Message-ID: <66fe41fb-6479-4ae1-a5dc-3ee78a2dffe6@bootlin.com> (raw)
In-Reply-To: <e46a9e5e10cbb28925025cb68d3c33e6a3292fab.1699266393.git.bluelightning@bluelightning.org>
Hi Paul
On 06.11.23 at 11:29, Paul Eggleton wrote:
> Security Fixes in 4.3
> ~~~~~~~~~~~~~~~~~~~~~
>
> +- bind: :cve:`2023-2911`, :cve:`2023-2828`, :cve:`2023-3341`, :cve:`2023-4236`
Oops, I realize that in the docs we usually use two spaces after "-",
though its not required by Sphinx. However, the script doesn't do that.
That was already the case for previous release notes.
I fixed that manually, but I don't think I'll modify past release notes.
If the script could do that too, that would be nice to have... Not
urgent at all, of course! I can ask again when a future point release is
made.
Thanks
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-11-06 17:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 10:29 [PATCH 00/12] 4.3 release documentation Paul Eggleton
2023-11-06 10:29 ` [PATCH 01/12] Remove references to apm in MACHINE_FEATURES Paul Eggleton
2023-11-06 10:29 ` [PATCH 02/12] ref-manual: update SDK_NAME variable documentation Paul Eggleton
2023-11-06 10:29 ` [PATCH 03/12] ref-manual: remove semicolons from *PROCESS_COMMAND variables Paul Eggleton
2023-11-06 10:29 ` [PATCH 04/12] release-notes-4.3: fix some typos Paul Eggleton
2023-11-06 10:29 ` [PATCH 05/12] release-notes-4.3: tweaks to existing text Paul Eggleton
2023-11-06 16:55 ` [docs] " Michael Opdenacker
2023-11-06 10:29 ` [PATCH 06/12] release-notes-4.3: add CVEs, recipe upgrades, license changes, contributors Paul Eggleton
2023-11-06 17:07 ` Michael Opdenacker [this message]
2023-11-06 10:29 ` [PATCH 07/12] release-notes-4.3: remove the Distribution section Paul Eggleton
2023-11-06 10:29 ` [PATCH 08/12] release-notes-4.3: move new classes to Rust section Paul Eggleton
2023-11-06 10:29 ` [PATCH 09/12] release-notes-4.3: feature additions Paul Eggleton
2023-11-06 10:45 ` [docs] " Ulrich Ölmann
2023-11-06 16:14 ` Paul Eggleton
2023-11-06 10:29 ` [PATCH 10/12] migration-4.3: remove some unnecessary items Paul Eggleton
2023-11-06 10:29 ` [PATCH 11/12] migration-4.3: adjustments to existing text Paul Eggleton
2023-11-06 10:29 ` [PATCH 12/12] migration-4.3: additional migration items Paul Eggleton
2023-11-06 10:58 ` [docs] " Ulrich Ölmann
2023-11-06 16:16 ` Paul Eggleton
2023-11-06 20:45 ` Michael Opdenacker
2023-11-06 10:45 ` [PATCH 00/12] 4.3 release documentation 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=66fe41fb-6479-4ae1-a5dc-3ee78a2dffe6@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