From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: devel@edk2.groups.io, liming.gao@intel.com,
"announce@edk2.groups.io" <announce@edk2.groups.io>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "Laszlo Ersek (lersek@redhat.com)" <lersek@redhat.com>,
"leif.lindholm@linaro.org" <leif.lindholm@linaro.org>,
"afish@apple.com" <afish@apple.com>
Subject: Re: [edk2-devel] EDK II Stable Tag edk2-stable201911 will be created based on commit bd85bf54c268204c7a698a96f3ccd96cd77952cd
Date: Fri, 29 Nov 2019 10:52:33 +0100 [thread overview]
Message-ID: <a4ae7209-3d86-c862-d0be-c110f1fbdf0c@redhat.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E54AA80@SHSMSX104.ccr.corp.intel.com>
On 11/29/19 9:22 AM, Liming Gao via Groups.Io wrote:
> Hi, all
>
> Because edk2 project has applied Pull request and remove the write
> access, I can’t push new Stable Tag edk2-stable201911 to GitHub edk2
> repo. I will ask help for Michael Kinney as soon as possible.
This is unfortunate. Does that mean the CI system has to re-run and once
successful push the tag?
> Today, this stable tag edk2-stable201911 version is decided at
> bd85bf54c268204c7a698a96f3ccd96cd77952cd. Stable tag will be created
> before early of next week. Sorry for the late notice. Please be patient,
> and enjoy Thanksgiving Day.
Thanks for announcing it that way, since this doesn't block other
projects pending of EDK2 releases!
Regards,
Phil.
> *From:* devel@edk2.groups.io [mailto:devel@edk2.groups.io] *On Behalf Of
> *Liming Gao
> *Sent:* Friday, November 29, 2019 2:19 PM
> *To:* rfc@edk2.groups.io; devel@edk2.groups.io
> *Subject:* [edk2-devel] EDK II Stable Tag edk2-stable201911 will be
> created based on commit bd85bf54c268204c7a698a96f3ccd96cd77952cd
>
> 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.
>
> Thanks
>
> Liming
>
>
next prev parent reply other threads:[~2019-11-29 9:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15DB8DBA8DBFAFC5.14768@groups.io>
2019-11-29 8:22 ` EDK II Stable Tag edk2-stable201911 will be created based on commit bd85bf54c268204c7a698a96f3ccd96cd77952cd Liming Gao
2019-11-29 9:52 ` Philippe Mathieu-Daudé [this message]
2019-11-29 10:01 ` [edk2-devel] " Leif Lindholm
2019-12-02 1:02 ` Liming Gao
2019-11-29 6:18 Liming Gao
2019-11-29 7:41 ` [edk2-devel] " Laszlo Ersek
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=a4ae7209-3d86-c862-d0be-c110f1fbdf0c@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