From: "Demeter, Miki" <miki.demeter@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"abner.chang@amd.com" <abner.chang@amd.com>
Subject: Re: [edk2-devel] [IMPORTANT] February Release Reviews and Merges
Date: Thu, 9 Feb 2023 17:01:16 +0000 [thread overview]
Message-ID: <DS0PR11MB64455383ADA1C39B34D57B248DD99@DS0PR11MB6445.namprd11.prod.outlook.com> (raw)
In-Reply-To: <MN2PR12MB3966BA6B553D382211CE7C5EEAD99@MN2PR12MB3966.namprd12.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2535 bytes --]
Received. I will be incontact
-miki
--
Miki Demeter (she/her/Miki)
Security Researcher / FW Developer
FST
Intel Corporation
Co-Chair, Network of Intel African-Ancestry(NIA) - Oregon
NIA-Oregon<https://intel.sharepoint.com/sites/NIA>
Portland Women in Tech Best Speaker
miki.demeter@intel.com<mailto:miki.demeter@intel.com>
503.712.8030 (office)
971.248.0123 (cell)
From: devel@edk2.groups.io <devel@edk2.groups.io> on behalf of Chang, Abner via groups.io <abner.chang=amd.com@groups.io>
Date: Wednesday, February 8, 2023 at 9:12 PM
To: Demeter, Miki <miki.demeter@intel.com>, devel@edk2.groups.io <devel@edk2.groups.io>
Cc: Attar, AbdulLateef (Abdul Lateef) <AbdulLateef.Attar@amd.com>
Subject: Re: [edk2-devel] [IMPORTANT] February Release Reviews and Merges
[AMD Official Use Only - General]
Hi Miki,
Here is a submission waiting for maintainer/reviewer's review.
https://edk2.groups.io/g/devel/message/98927 (Adds AmdSmmCpuFeaturesLib for AMD Family)
Thanks
Abner
> -----Original Message-----
> From: discuss@edk2.groups.io <discuss@edk2.groups.io> On Behalf Of Demeter,
> Miki via groups.io
> Sent: Thursday, February 9, 2023 8:20 AM
> To: devel@edk2.groups.io; announce@edk2.groups.io; discuss@edk2.groups.io
> Subject: [edk2-discuss] [IMPORTANT] February Release Reviews and Merges
>
> Caution: This message originated from an External Source. Use proper caution
> when opening attachments, clicking links, or responding.
>
>
> Important Information About the February Release
>
> The Stewards are aware there has been an issue with getting patches reviewed
> and/or merged in a timely manner. The stewards are considering a delay to the
> February release to allow for these issues to be addressed.
>
> Please take the time to validate that your submissions to the email list fall into
> one of the two categories please contact me directly immediately and CC the
> mailing list
>
> [1] You have patches submitted to the mailing list requesting review with no
> response
>
> [2] You have patches submitted to the mailing list that have been reviewed but
> not merged for the February release
>
>
> Thank you
>
> --
> Miki Demeter (she/her/Miki)
> Security Researcher / FW Developer
> FST
> Intel Corporation
>
> Co-Chair, Network of Intel African-Ancestry(NIA) - Oregon NIA-
> Oregon<https://intel.sharepoint.com/sites/NIA>
>
> Portland Women in Tech Best Speaker
> miki.demeter@intel.com<mailto:miki.demeter@intel.com>
>
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 7802 bytes --]
next prev parent reply other threads:[~2023-02-09 17:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 0:20 [IMPORTANT] February Release Reviews and Merges Demeter, Miki
2023-02-09 5:11 ` Chang, Abner
2023-02-09 17:01 ` Demeter, Miki [this message]
2023-02-13 0:58 ` [edk2-devel] " Chang, Abner
2023-02-09 17:06 ` Ard Biesheuvel
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=DS0PR11MB64455383ADA1C39B34D57B248DD99@DS0PR11MB6445.namprd11.prod.outlook.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