From: "Leif Lindholm" <quic_llindhol@quicinc.com>
To: Kun Qin <kuqin12@gmail.com>, <devel@edk2.groups.io>
Cc: Andrew Fish <afish@apple.com>,
Michael D Kinney <michael.d.kinney@intel.com>,
Miki Demeter <miki.demeter@intel.com>,
Sean Brogan <sean.brogan@microsoft.com>
Subject: Re: [PATCH v1 0/1] Define security policy in SECURITY.md file for repository
Date: Wed, 5 Apr 2023 19:07:36 +0100 [thread overview]
Message-ID: <a110db41-fb44-089d-4e23-fed50efe514a@quicinc.com> (raw)
In-Reply-To: <20230309194351.1024-1-kuqin12@gmail.com>
On 2023-03-09 19:43, Kun Qin wrote:
> This change added a markdown file as a policy guideline for Tianocore EDK2
> community to handle security sensitive reports.
>
> Patch v1 branch: https://github.com/kuqin12/edk2/tree/patch-1
>
> Cc: Andrew Fish <afish@apple.com>
> Cc: Leif Lindholm <quic_llindhol@quicinc.com>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
> Cc: Miki Demeter <miki.demeter@intel.com>
> Cc: Sean Brogan <sean.brogan@microsoft.com>
>
> Sean Brogan (1):
> Define security policy in SECURITY.md file for repository
>
> SECURITY.md | 33 ++++++++++++++++++++
> 1 file changed, 33 insertions(+)
> create mode 100644 SECURITY.md
Nitpick: edk2 is alternaltingly capitalised or not in the readme.
But
Reviewed-by: Leif Lindholm <quic_llindhol@quicinc.com>
prev parent reply other threads:[~2023-04-05 18:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 19:43 [PATCH v1 0/1] Define security policy in SECURITY.md file for repository Kun Qin
2023-03-09 19:43 ` [PATCH v1 1/1] " Kun Qin
2023-03-28 12:15 ` [edk2-devel] " Rebecca Cran
2023-03-28 0:26 ` [PATCH v1 0/1] " Demeter, Miki
2023-03-28 16:50 ` [edk2-devel] " Kevin@Insyde
2023-04-05 18:07 ` Leif Lindholm [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-list 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=a110db41-fb44-089d-4e23-fed50efe514a@quicinc.com \
--to=devel@edk2.groups.io \
/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