From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, leif.lindholm@linaro.org, "Wu,
Hao A" <hao.a.wu@intel.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
Andrew Fish <afish@apple.com>,
"Justen, Jordan L" <jordan.l.justen@intel.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
"Gao, Liming" <liming.gao@intel.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
"Zeng, Star" <star.zeng@intel.com>
Subject: Re: [edk2-devel] [RFC] Fine-grained review ownership for MdeModulePkg
Date: Thu, 20 Jun 2019 17:43:08 +0200 [thread overview]
Message-ID: <e2fb26b5-7bcf-23cf-5a69-d886e7bdee89@redhat.com> (raw)
In-Reply-To: <20190619093533.ueex63rrkovdhyz2@bivouac.eciton.net>
On 06/19/19 11:35, Leif Lindholm wrote:
> On Wed, Jun 19, 2019 at 05:09:40AM +0000, Wu, Hao A wrote:
>> Hello all,
>>
>> As suggested by Ray and Leif, modules (with wildcard) in MdeModulePkg are
>> classified to a list of features.
>>
>> Please note that:
>> * The below list is a draft at this moment, please help to provide
>> feedbacks/comments;
>> * Modules with no clear classification are listed under the 'Misc' section
>> at the bottom of the list.
>
> Thank you for doing the heavy lifting.
+1
> A few comments below on how this could be more easily described in the
> Maintainer.txt syntax.
With Leif's comments addressed, I'd be super pleased to have this
pattern list for covering MdeModulePkg, minimally as a starting point.
(I'm neutral on moving around GraphicsOutputDxe and Logo -- we could do
that now, or as a later improvement.)
Thanks!
Laszlo
next prev parent reply other threads:[~2019-06-20 15:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 8:06 [RFC] Fine-grained review ownership for MdeModulePkg Wu, Hao A
2019-06-11 9:51 ` Leif Lindholm
2019-06-11 15:41 ` Laszlo Ersek
2019-06-19 5:09 ` Wu, Hao A
2019-06-19 9:35 ` Leif Lindholm
2019-06-20 15:43 ` Laszlo Ersek [this message]
2019-06-24 1:16 ` [edk2-devel] " Wu, Hao A
2019-06-24 20:29 ` Laszlo Ersek
2019-06-24 22:58 ` Yao, Jiewen
2019-07-16 13:53 ` Leif Lindholm
2019-07-17 1:47 ` Wu, Hao A
2019-06-20 22:23 ` rebecca
2019-06-21 0:11 ` Wu, Hao A
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=e2fb26b5-7bcf-23cf-5a69-d886e7bdee89@redhat.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