From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, liming.gao@intel.com,
"rfc@edk2.groups.io" <rfc@edk2.groups.io>
Subject: Re: [edk2-devel] EDK II Stable Tag edk2-stable201911 will be created based on commit bd85bf54c268204c7a698a96f3ccd96cd77952cd
Date: Fri, 29 Nov 2019 08:41:50 +0100 [thread overview]
Message-ID: <068cd96f-5fcc-f6a2-f172-25d6fc99b290@redhat.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E54A94E@SHSMSX104.ccr.corp.intel.com>
On 11/29/19 07:18, Liming Gao via Groups.Io wrote:
> Hi, all
>
> Today, I review all patches in edk2 mail list. There is no patches for EDK II Stable Tag edk2-stable201911. Based on edk2-stable201911 tag planning, it will be released at 2019-11-29. So, I plan to create edk2-stable201911 based on current edk2 trunk (the latest commit https://github.com/tianocore/edk2/commit/bd85bf54c268204c7a698a96f3ccd96cd77952cd MdeModulePkg/Variable: Initialize local variable "RtPtrTrack"). If you have any comments, please reply the mail. If no concern or objection, I will create tag and send another announce mail that edk2-stable201911 is completed and normal commit is resumed.
No objection from me.
Thank you for managing the SFF / HFF process, and the release, again,
Liming!
Laszlo
next prev parent reply other threads:[~2019-11-29 7:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 6:18 EDK II Stable Tag edk2-stable201911 will be created based on commit bd85bf54c268204c7a698a96f3ccd96cd77952cd Liming Gao
2019-11-29 7:41 ` Laszlo Ersek [this message]
[not found] <15DB8DBA8DBFAFC5.14768@groups.io>
2019-11-29 8:22 ` Liming Gao
2019-11-29 9:52 ` [edk2-devel] " Philippe Mathieu-Daudé
2019-11-29 10:01 ` Leif Lindholm
2019-12-02 1:02 ` Liming Gao
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=068cd96f-5fcc-f6a2-f172-25d6fc99b290@redhat.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