From: "Rebecca Cran" <quic_rcran@quicinc.com>
To: "Demeter, Miki" <miki.demeter@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"announce@edk2.groups.io" <announce@edk2.groups.io>
Subject: Re: [edk2-announce] TianoCore Community Meeting February 2022
Date: Fri, 11 Feb 2022 14:11:42 -0700 [thread overview]
Message-ID: <b0d804d0-22da-ef37-5424-408f57ff5c4f@quicinc.com> (raw)
In-Reply-To: <FB9DF38F-2531-41E7-8103-CF98C6C8E27E@intel.com>
On 2/10/22 21:10, Demeter, Miki wrote:
> - New Coverity Version in Feb. Michael and Felix to work on a process to disposition issues.
https://scan.coverity.com/projects/tianocore-edk2 says the code was last
scanned in August 2020.
--
Rebecca Cran
next prev parent reply other threads:[~2022-02-11 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 4:10 TianoCore Community Meeting February 2022 Demeter, Miki
2022-02-11 21:11 ` Rebecca Cran [this message]
2022-02-11 21:34 ` [edk2-announce] " Demeter, Miki
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=b0d804d0-22da-ef37-5424-408f57ff5c4f@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