From: Laszlo Ersek <lersek@redhat.com>
To: "Gao, Liming" <liming.gao@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"Cetola, Stephano" <stephano.cetola@intel.com>,
"leif.lindholm@linaro.org" <leif.lindholm@linaro.org>,
"afish@apple.com" <afish@apple.com>
Subject: Re: [edk2-announce] EDK II Stable Tag edk2-stable201811 will be created based on commit 85588389222a3636baf0f9ed8227f2434af4c3f9
Date: Wed, 14 Nov 2018 16:38:50 +0100 [thread overview]
Message-ID: <13b079e2-bfb9-a221-9fe4-c71948b334c9@redhat.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E36BA2D@SHSMSX104.ccr.corp.intel.com>
On 11/14/18 15:20, Gao, Liming wrote:
> Hi, all Today, I review all patches in edk2 mail list. There is no
> patches for EDK II Stable Tag edk2-stable201811. Based on
> edk2-stable201811 tag planning, it will be released at 2018-11-15.
> So, I plan to create edk2-stable201811 based on current edk2 trunk
> (the latest commit
> https://github.com/tianocore/edk2/commit/85588389222a3636baf0f9ed8227f2434af4c3f9
> UefiCpuPkg/CommonFeature: Always set FEATURE_CONTROL.Lock) on China
> time (UTC + 8) 12:00PM of 2018-11-15. 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-stable201811 is completed
> and normal commit is resumed.
Sounds good to me, thank you.
Laszlo
next prev parent reply other threads:[~2018-11-14 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 14:20 [edk2-announce] EDK II Stable Tag edk2-stable201811 will be created based on commit 85588389222a3636baf0f9ed8227f2434af4c3f9 Gao, Liming
2018-11-14 15:38 ` Laszlo Ersek [this message]
2018-11-14 18:15 ` Kinney, Michael D
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=13b079e2-bfb9-a221-9fe4-c71948b334c9@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