($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: "Lee, Chee Yang" <chee.yang.lee@intel.com>
To: "michael.opdenacker@bootlin.com" <michael.opdenacker@bootlin.com>
Cc: "docs@lists.yoctoproject.org" <docs@lists.yoctoproject.org>
Subject: RE: [docs] [PATCH] release-notes-4.0.17: reorder CVEs
Date: Fri, 29 Mar 2024 03:12:09 +0000	[thread overview]
Message-ID: <CH3PR11MB80933F43D2EF6AE2E343BA18B93A2@CH3PR11MB8093.namprd11.prod.outlook.com> (raw)
In-Reply-To: <2fcb0eff-8a38-4238-94f7-44cfbb8a8cd9@bootlin.com>



> -----Original Message-----
> From: docs@lists.yoctoproject.org <docs@lists.yoctoproject.org> On Behalf Of
> Michael Opdenacker via lists.yoctoproject.org
> Sent: Thursday, March 28, 2024 10:42 PM
> To: Lee, Chee Yang <chee.yang.lee@intel.com>
> Cc: docs@lists.yoctoproject.org
> Subject: Re: [docs] [PATCH] release-notes-4.0.17: reorder CVEs
> 
> Hi Lee
> 
> On 3/28/24 at 03:31, Lee Chee Yang wrote:
> > From: Lee Chee Yang <chee.yang.lee@intel.com>
> >
> > reorder CVEs from alphabetical order to numerical order, align it with
> > text based release notes.
> >
> > Signed-off-by: Lee Chee Yang <chee.yang.lee@intel.com>
> 
> Makes for this update!
> Are the CVEs now automatically sorted by your scripts?
My script converting text to rst reorder CVEs in alphabetical order. 
I have updated that script.

> 
> Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Merged
> into master-next.
> Cheers
> Michael.
> 
> --
> Michael Opdenacker, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com


      reply	other threads:[~2024-03-29  3:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28  2:31 [PATCH] release-notes-4.0.17: reorder CVEs chee.yang.lee
2024-03-28 14:41 ` [docs] " Michael Opdenacker
2024-03-29  3:12   ` Lee, Chee Yang [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=CH3PR11MB80933F43D2EF6AE2E343BA18B93A2@CH3PR11MB8093.namprd11.prod.outlook.com \
    --to=chee.yang.lee@intel.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=michael.opdenacker@bootlin.com \
    /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).