From: "Michael Kubacki" <mikuback@linux.microsoft.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: Liming Gao <gaoliming@byosoft.com.cn>,
Michael D Kinney <michael.d.kinney@intel.com>
Subject: [RFC] Git tag after extended hard freeze
Date: Mon, 29 Nov 2021 23:00:17 -0500 [thread overview]
Message-ID: <773b00cb-174b-9ef1-acce-ed681e45879a@linux.microsoft.com> (raw)
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 reply other threads:[~2021-11-30 4:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 4:00 Michael Kubacki [this message]
2021-12-01 1:56 ` 回复: [edk2-devel] [RFC] Git tag after extended hard freeze gaoliming
2021-12-01 2:13 ` 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=773b00cb-174b-9ef1-acce-ed681e45879a@linux.microsoft.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