All of lore.kernel.org
 help / color / mirror / Atom feed
* Re: [docs] [PATCH] migration guides: release notes for 4.0.2
       [not found] <20220708112633.2761010-1-chee.yang.lee@intel.com>
@ 2022-07-18 16:52 ` Michael Opdenacker
  0 siblings, 0 replies; only message in thread
From: Michael Opdenacker @ 2022-07-18 16:52 UTC (permalink / raw)
  To: Lee Chee Yang; +Cc: docs

Hi Lee

Many thanks for these new release notes in Sphinx format! This really 
made things simpler :)
See my minor comments below.

On 7/8/22 13:26, Lee Chee Yang wrote:
> +++ b/documentation/migration-guides/release-notes-4.0.2.rst
...
>
> +yocto-docs
> +
> +-  Repository Location: https://git.yoctoproject.org/git/yocto-docs
> +-  Branch: :yocto_git:`kirkstone </yocto-docs/log/?h=kirkstone>`
> +-  Tag: :yocto_git:`yocto-4.0.2 </yocto-docs/log/?h=yocto-4.0.2>`
> +-  Git Revision: :yocto_git:`TBD </yocto-docs/commit/?id=662294dccd028828d5c7e9fd8f5c8e14df53df4b>`


Oops, your script (I assume) generated "TBD" instead of the commit id 
here. I fixed it manually this time.

> +
> +Security Fixes in Yocto-4.0.2
> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> +
> +-  libxslt: Mark :cve:`2022-29824` as not applying
> +-  tiff: Add jbig PACKAGECONFIG and clarify IGNORE :cve:`2022-1210`
> +-  tiff: mark :cve:`2022-1622` and :cve:`2022-1623` as invalid
> +-  pcre2:fix :cve:`2022-1586` Out-of-bounds read
> +-  curl: fix :cve:`2022-22576` :cve:`2022-27775` :cve:`2022-27776` :cve:`2022-27774` :cve:`2022-30115` :cve:`2022-27780` :cve:`2022-27781` :cve:`2022-27779` :cve:`2022-27782`
> +-  qemu: fix :cve:`2021-4206` :cve:`2021-4207`
> +-  freetype: fix :cve:`2022-27404` :cve:`2022-27405` :cve:`2022-27406`


When multiple CVEs are referred to, would it be possible to add commas 
between them, and "and" before the last one? No problem for me to do 
this manually for the moment.

Last thing... Would it be possible to change the order of the sections, 
like in the previous Sphinx release notes? I think that the most 
relevant information (fixes and changes) should come first. Here's the 
order I've used so far:

 1. Security fixes
 2. Fixes
 3. Known issues
 4. Contributors
 5. Repositories / Downloads

I made the changes manually again, no problem.
Your commit is now in master-next.

Many thanks again
Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2022-07-18 16:52 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <20220708112633.2761010-1-chee.yang.lee@intel.com>
2022-07-18 16:52 ` [docs] [PATCH] migration guides: release notes for 4.0.2 Michael Opdenacker

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.