From: "Michael Kubacki" <mikuback@linux.microsoft.com>
To: gaoliming <gaoliming@byosoft.com.cn>, devel@edk2.groups.io
Cc: 'Michael D Kinney' <michael.d.kinney@intel.com>
Subject: Re: 回复: [edk2-devel] [RFC] Git tag after extended hard freeze
Date: Tue, 30 Nov 2021 21:13:28 -0500 [thread overview]
Message-ID: <3a010965-1749-9263-fb7c-16433daa0b1e@linux.microsoft.com> (raw)
In-Reply-To: <000b01d7e656$a06ddf10$e1499d30$@byosoft.com.cn>
Inclusion in the next stable tag doesn't provide an explicit reference
for those that wish to adopt edk2-stable202111 + Uncrustify. This will
likely be a relatively common path since if you wait until
edk2-stable202202:
1) local source code will be very different from the upstream impacting
diffs and contributions in the meantime
2) the actual changes that occurred during the edk2-stable202202 time
frame will be much easier to diff against the
edk2-stable202111-uncrustify tag than the edk2-stable202111 tag alone
Integration of edk2-stable202111 + Uncrustify can of course be done
without the tag but I think it would be meaningful and help better
designate a common upstream integration point.
Yes, I can consolidate information present in several places at the
moment into a single wiki page.
Thanks,
Michael
On 11/30/2021 8:56 PM, gaoliming wrote:
> 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
>>
>>
>>
>>
>
>
prev parent reply other threads:[~2021-12-01 2:13 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 ` 回复: [edk2-devel] " gaoliming
2021-12-01 2:13 ` Michael Kubacki [this message]
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=3a010965-1749-9263-fb7c-16433daa0b1e@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