From: "Kinney, Michael D" <michael.d.kinney@intel.com>
To: "Richardson, Brian" <brian.richardson@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: UDK2017 pre-release info now on wiki
Date: Tue, 2 May 2017 19:57:38 +0000 [thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F57D17009F@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <80AC2BAA3152784F98F581129E5CF5AF8DF24C18@ORSMSX109.amr.corp.intel.com>
Brian,
Thanks for the summary of features in UDK 2017.
I want to encourage everyone in the EDK II community to
checkout the UDK2017 branch and test their platforms,
drivers, applications, and operating systems.
https://github.com/tianocore/edk2/tree/UDK2017
If you see issues, please enter Bugzilla issues so these
Issues can be addressed and improve the quality of the
UDK 2017 release.
https://bugzilla.tianocore.org/
Thanks,
Mike
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Richardson,
> Brian
> Sent: Friday, April 28, 2017 10:59 AM
> To: edk2-devel@lists.01.org
> Subject: [edk2] UDK2017 pre-release info now on wiki
>
> Information on UDK2017, the next stable snapshot release of EDK II, is available on
> the TianoCore wiki.
>
> https://github.com/tianocore/tianocore.github.io/wiki/UDK2017
>
> Thanks ... br
> ---
> Brian Richardson, Senior Technical Marketing Engineer, Intel Software
> brian.richardson@intel.com<mailto:brian.richardson@intel.com> -- @intel_brian (Twitter
> & WeChat)
> https://software.intel.com/en-us/meet-the-developers/evangelists/team/brian-richardson
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2017-05-02 19:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 17:58 UDK2017 pre-release info now on wiki Richardson, Brian
2017-05-02 19:57 ` Kinney, Michael D [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=E92EE9817A31E24EB0585FDF735412F57D17009F@ORSMSX113.amr.corp.intel.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