public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Kubacki, Michael A" <michael.a.kubacki@intel.com>
To: "Ni, Ray" <ray.ni@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] [edk2-rfc] [edk2-platforms] Add Features directory
Date: Thu, 21 Nov 2019 23:11:56 +0000	[thread overview]
Message-ID: <BY5PR11MB4484CB8C07F08FAEEE7715B6B54E0@BY5PR11MB4484.namprd11.prod.outlook.com> (raw)
In-Reply-To: <16528.1574323507806442601@groups.io>

[-- Attachment #1: Type: text/plain, Size: 848 bytes --]

I think the plural name is more intuitive since there will be more than one feature but I don’t have a strong preference.

Thanks,
Michael

From: Ni, Ray <ray.ni@intel.com>
Sent: Thursday, November 21, 2019 12:05 AM
To: Kubacki; Kubacki, Michael A <michael.a.kubacki@intel.com>; devel@edk2.groups.io
Subject: Re: [edk2-devel] [edk2-rfc] [edk2-platforms] Add Features directory


Basically I think the "/Features" directory is a good idea. It separates the common features from the concrete platforms. Minor comment: Given today here are "Drivers", "Platform" and "Silicon" under the root of edk2-platforms repo, do you think that it's better to use "/Feature" to align existing names?

I also wanted to change "Drivers" to "Driver" (https://edk2.groups.io/g/devel/message/47203?p=,,,20,0,0,0::Created,,OptionRomPkg,20,2,0,33080721)

[-- Attachment #2: Type: text/html, Size: 3463 bytes --]

  reply	other threads:[~2019-11-21 23:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-02  0:18 [edk2-rfc] [edk2-platforms] Add Features directory Kubacki, Michael A
2019-11-21  8:05 ` [edk2-devel] " Ni, Ray
2019-11-21 23:11   ` Kubacki, Michael A [this message]
2019-11-22  1:17     ` Ni, Ray

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=BY5PR11MB4484CB8C07F08FAEEE7715B6B54E0@BY5PR11MB4484.namprd11.prod.outlook.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