From: "Ni, Ray" <ray.ni@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Ni, Ray" <ray.ni@intel.com>,
"'philmd@redhat.com'" <philmd@redhat.com>,
"leif.lindholm@linaro.org" <leif.lindholm@linaro.org>,
"Justen, Jordan L" <jordan.l.justen@intel.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Stefan Berger" <stefanb@linux.ibm.com>,
"Anthony Perard" <anthony.perard@citrix.com>,
"Julien Grall" <julien.grall@arm.com>
Cc: "Feng, Bob C" <bob.c.feng@intel.com>,
"Gao, Liming" <liming.gao@intel.com>,
Andrew Fish <afish@apple.com>, Laszlo Ersek <lersek@redhat.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Wu, Hao A" <hao.a.wu@intel.com>
Subject: Re: [edk2-devel] [RFC PATCH 1/3] Maintainers.txt: update for filesystem area descriptions
Date: Tue, 18 Jun 2019 05:32:38 +0000 [thread overview]
Message-ID: <734D49CCEBEEF84792F5B80ED585239D5C1D58CA@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <15A92D638F8524EE.27464@groups.io>
Even the five people claims to be the maintainers of all TPM2 modules, I still think
the maintainers.txt is not very human readable.
I suggest a txt file as below:
MdePkg
......
F: MdePkg/Include/IndustryStandard/Tpm2*
R: Marc-André Lureau <marcandre.lureau@redhat.com>
R: Stefan Berger <stefanb@linux.ibm.com>
SecurityPkg
......
F: SecurityPkg/*/Tpm2*
R: Marc-André Lureau <marcandre.lureau@redhat.com>
R: Stefan Berger <stefanb@linux.ibm.com>
So developers who change a certain package can firstly find the
correct package section, then check F-tag to understand who
are the maintainers and reviewers.
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Ni, Ray
> Sent: Tuesday, June 18, 2019 11:31 AM
> To: devel@edk2.groups.io; 'philmd@redhat.com' <philmd@redhat.com>;
> leif.lindholm@linaro.org; Justen, Jordan L <jordan.l.justen@intel.com>;
> Marc-André Lureau <marcandre.lureau@redhat.com>; Stefan Berger
> <stefanb@linux.ibm.com>; Anthony Perard <anthony.perard@citrix.com>;
> Julien Grall <julien.grall@arm.com>
> Cc: Feng, Bob C <bob.c.feng@intel.com>; Gao, Liming
> <liming.gao@intel.com>; Andrew Fish <afish@apple.com>; Laszlo Ersek
> <lersek@redhat.com>; Kinney, Michael D <michael.d.kinney@intel.com>;
> Wu, Hao A <hao.a.wu@intel.com>
> Subject: Re: [edk2-devel] [RFC PATCH 1/3] Maintainers.txt: update for
> filesystem area descriptions
>
> > +
> > +OvmfPkg (TPM2 modules)
>
> How about just say "TPM2 modules"?
>
> > +F: MdePkg/Include/IndustryStandard/Tpm2*
> > +F: SecurityPkg/*/Tpm2*
> > +M: Jordan Justen <jordan.l.justen@intel.com>
> > +M: Laszlo Ersek <lersek@redhat.com>
> > +M: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> > R: Marc-André Lureau <marcandre.lureau@redhat.com>
> > - (TPM2 modules)
> > R: Stefan Berger <stefanb@linux.ibm.com>
> > - (TPM2 modules)
> > S: Maintained
> > ---
> >
> > Although TPM2 deserves its own section IMHO.
> > (Ditto with ArmVirtPkg Xen).
>
>
>
next prev parent reply other threads:[~2019-06-18 5:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 20:21 [RFC PATCH 1/3] Maintainers.txt: update for filesystem area descriptions Leif Lindholm
2019-06-15 6:01 ` [edk2-devel] " Philippe Mathieu-Daudé
2019-06-18 3:30 ` Ni, Ray
[not found] ` <15A92D638F8524EE.27464@groups.io>
2019-06-18 5:32 ` Ni, Ray [this message]
2019-06-18 11:17 ` Leif Lindholm
2019-06-20 15:13 ` Laszlo Ersek
2019-06-20 15:22 ` Leif Lindholm
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=734D49CCEBEEF84792F5B80ED585239D5C1D58CA@SHSMSX104.ccr.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