From: "gaoliming" <gaoliming@byosoft.com.cn>
To: <devel@edk2.groups.io>, <mikuback@linux.microsoft.com>
Cc: "'Michael D Kinney'" <michael.d.kinney@intel.com>
Subject: 回复: [edk2-devel] [RFC] Git tag after extended hard freeze
Date: Wed, 1 Dec 2021 09:56:16 +0800 [thread overview]
Message-ID: <000b01d7e656$a06ddf10$e1499d30$@byosoft.com.cn> (raw)
In-Reply-To: <773b00cb-174b-9ef1-acce-ed681e45879a@linux.microsoft.com>
Michael:
Next stable tag 202202 will include these changes. We can introduce this feature into next stable tag release note.
Besides, do you plan to write one wiki page to introduce Uncrustify features and changes? If so, this wiki can be linked to the stable tag release note.
Thanks
Liming
> -----邮件原件-----
> 发件人: devel@edk2.groups.io <devel@edk2.groups.io> 代表 Michael
> Kubacki
> 发送时间: 2021年11月30日 12:00
> 收件人: devel@edk2.groups.io
> 抄送: Liming Gao <gaoliming@byosoft.com.cn>; Michael D Kinney
> <michael.d.kinney@intel.com>
> 主题: [edk2-devel] [RFC] Git tag after extended hard freeze
>
> The edk2-stable202111 tag was created on commit bb1bba3 on Nov 26th
> 2021
> as described in
> https://github.com/tianocore/edk2/releases/tag/edk2-stable202111.
>
> During the ongoing extended hard freeze, several changes related to code
> formatting and CI plugins are being applied as described in
> https://edk2.groups.io/g/devel/message/84132.
>
> Since the code has already been tagged prior to these changes, I would
> like to see if a tag can also be applied after the extended hard freeze
> changes are complete. The tag would be a useful reference for those
> interested in integrating the Uncrustify changes with the previously
> tagged edk2-stable202111 code.
>
> Regards,
> Michael
>
>
>
>
next prev parent reply other threads:[~2021-12-01 1:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 4:00 [RFC] Git tag after extended hard freeze Michael Kubacki
2021-12-01 1:56 ` gaoliming [this message]
2021-12-01 2:13 ` 回复: [edk2-devel] " Michael Kubacki
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='000b01d7e656$a06ddf10$e1499d30$@byosoft.com.cn' \
--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