public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Kinney, Michael D" <michael.d.kinney@intel.com>
To: "Kubacki, Michael A" <michael.a.kubacki@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: Intel Platforms in Bugzilla
Date: Wed, 20 Feb 2019 19:05:14 +0000	[thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5B8BB1E9B@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <49AB4ACB9627B8468F29D589A27B7455844DEDEA@ORSMSX121.amr.corp.intel.com>

Hi Michael,

Done.  Some of these new components need more detailed descriptions.
Please follow up with how you want those filled in.

Thanks,

Mike

> -----Original Message-----
> From: Kubacki, Michael A
> Sent: Tuesday, February 19, 2019 5:31 PM
> To: edk2-devel@lists.01.org
> Cc: Kinney, Michael D <michael.d.kinney@intel.com>
> Subject: Intel Platforms in Bugzilla
> 
> Hi Mike,
> 
> The devel-MinPlatform branch in the edk2-platforms repo
> is being used to develop Intel platform code. We plan
> to move this work to the master branch in edk2-
> platforms after a refactor in the MinPlatformPkg.
> 
> There's a need to submit feature requests and bugs
> against this code now. Do you think we could add the
> AdvancedFeaturePkg, ClevoOpenBoardPkg,
> KabylakeOpenBoardPkg, MinPlatformPkg, and
> PurleyOpenBoardPkg to the EDK2 Platforms product on
> Bugzilla?
> 
> Regards,
> Michael



      reply	other threads:[~2019-02-20 19:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-20  1:31 Intel Platforms in Bugzilla Kubacki, Michael A
2019-02-20 19:05 ` 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=E92EE9817A31E24EB0585FDF735412F5B8BB1E9B@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