From: "liyi 00215672" <phoenix.liyi@Huawei.com>
To: Rebecca Cran <rebecca@bluestop.org>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"lersek@redhat.com" <lersek@redhat.com>
Subject: 答复: [edk2-devel] Requestion for LTS version on EDK2
Date: Wed, 24 Apr 2019 00:46:33 +0000 [thread overview]
Message-ID: <cf2e286808f94ed1b324d1c9552fc290@huawei.com> (raw)
In-Reply-To: <f26207ba-726f-35e3-a6bc-c4ce900d7884@bluestop.org>
It seems the UDK branch only merged some common and x86-specific patches , the non-x86 patches would not be merged into UDK branch.
So under my understanding ,the UDK is suitable only for x86 arch.
Thanks.
Lee
-----邮件原件-----
发件人: Rebecca Cran [mailto:rebecca@bluestop.org]
发送时间: 2019年4月24日 1:53
收件人: devel@edk2.groups.io; lersek@redhat.com; liyi 00215672 <phoenix.liyi@huawei.com>
主题: Re: [edk2-devel] Requestion for LTS version on EDK2
On 2019-04-18 17:26, Laszlo Ersek wrote:
>
> (1) Introduce stable *branches* to the development model. Those would
> be forked off at the stable tags (well, at some of them).
Would this be _re_ introducing stable branches? As explained in https://github.com/tianocore/tianocore.github.io/wiki/UDK it seems the project only recently moved from UDK<year> stable branches (at least, I took them to be stable branches) to periodically tagging master with a stable tag.
--
Rebecca Cran
next prev parent reply other threads:[~2019-04-24 0:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 7:17 Requestion for LTS version on EDK2 liyi 00215672
2019-04-18 23:26 ` [edk2-devel] " Laszlo Ersek
2019-04-19 11:11 ` liyi 00215672
2019-04-23 11:10 ` Laszlo Ersek
2019-04-23 14:30 ` 答复: " liyi 00215672
2019-04-24 9:57 ` Laszlo Ersek
2019-04-23 17:52 ` rebecca
2019-04-24 0:46 ` liyi 00215672 [this message]
2019-04-24 10:01 ` 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=cf2e286808f94ed1b324d1c9552fc290@huawei.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