From: "Leif Lindholm" <leif.lindholm@linaro.org>
To: devel@edk2.groups.io
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Michael D Kinney <michael.d.kinney@intel.com>
Subject: [PATCH edk2-platforms 1/6] Maintainers.txt: Update documentation for new format
Date: Wed, 9 Oct 2019 13:00:08 +0100 [thread overview]
Message-ID: <20191009120013.28076-2-leif.lindholm@linaro.org> (raw)
In-Reply-To: <20191009120013.28076-1-leif.lindholm@linaro.org>
Synchronize header with edk2/Maintainers.txt and change references
from "EDK II to EDK II Platforms".
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Signed-off-by: Leif Lindholm <leif.lindholm@linaro.org>
---
Maintainers.txt | 42 +++++++++++++++++++++++++++++++++---------
1 file changed, 33 insertions(+), 9 deletions(-)
diff --git a/Maintainers.txt b/Maintainers.txt
index 1260c8d2465b..f824e2b05de1 100644
--- a/Maintainers.txt
+++ b/Maintainers.txt
@@ -1,17 +1,24 @@
-EDK II Maintainers
-==================
+EDK II Platforms Maintainers
+============================
This file provides information about the primary maintainers for
-EDK II Platforms.
+EDK Platforms II.
In general, you should not privately email the maintainer. You should
-email the edk2-devel list, but you can also Cc the maintainer.
+email the edk2-devel list, and Cc the package maintainers and
+reviewers.
+
+If the package maintainer wants to hand over the role to other people,
+the package maintainer should send the patch to update Maintainers.txt
+with new maintainer, and the new maintainer should follow up with
+an Acked-by or a Reviewed-by.
Descriptions of section entries:
L: Mailing list that is relevant to this area (default is edk2-devel)
Patches and questions should be sent to the email list.
- M: Cc address for patches and questions (ie, the package maintainer)
+ M: Package Maintainer: Cc address for patches and questions. Responsible
+ for reviewing and pushing package changes to source control.
R: Package Reviewer: Cc address for patches and questions. Reviewers help
maintainers review code, but don't have push access. A designated Package
Reviewer is reasonably familiar with the Package (or some modules
@@ -29,9 +36,26 @@ Descriptions of section entries:
Obsolete: Old code. Something tagged obsolete generally means
it has been replaced by a better system and you
should be using that.
+ F: Files and directories with wildcard patterns.
+ A trailing slash includes all files and subdirectory files.
+ F: MdeModulePkg/ all files in and below MdeModulePkg
+ F: MdeModulePkg/* all files in MdeModulePkg, but not below
+ F: */Pci/* all files in a directory called Pci, at any depth in
+ the hierarchy, but not below
+ One pattern per line. Multiple F: lines per section acceptable.
+ X: Files and directories that are NOT maintained, same rules as F:
+ Files exclusions are tested after file matches.
+ Can be useful for excluding a specific subdirectory, for instance:
+ F: NetworkPkg/
+ X: NetworkPkg/Ip6Dxe/
+ matches all files in and below NetworkPkg excluding NetworkPkg/Ip6Dxe/
+ Filenames not caught by any F: rule get matched as being located in the top-
+ level directory. (Internally, the script looks for a match called '<default>',
+ so please don't add a file called that in the top-level directory.)
-EDK II
-------
+
+EDK II Platforms
+----------------
W: https://github.com/tianocore/tianocore.github.io/wiki/EDK-II
L: https://edk2.groups.io/g/devel/
T: git - https://github.com/tianocore/edk2-platforms.git
@@ -40,8 +64,8 @@ Responsible Disclosure, Reporting Security Issues
-------------------------------------------------
W: https://github.com/tianocore/tianocore.github.io/wiki/Security
-EDK II Packages:
-----------------
+EDK II Platforms Packages:
+--------------------------
Drivers/OptionRomPkg
W: https://github.com/tianocore/tianocore.github.io/wiki/OptionRomPkg
--
2.20.1
next prev parent reply other threads:[~2019-10-09 12:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 12:00 [PATCH edk2-platforms 0/6] Update Maintainers.txt Leif Lindholm
2019-10-09 12:00 ` Leif Lindholm [this message]
2019-10-09 12:51 ` [edk2-devel] [PATCH edk2-platforms 1/6] Maintainers.txt: Update documentation for new format Philippe Mathieu-Daudé
2019-10-09 12:54 ` Leif Lindholm
2019-10-09 12:59 ` Philippe Mathieu-Daudé
2019-10-09 12:00 ` [PATCH edk2-platforms 2/6] Maintainers.txt: drop ',' from maintainer names Leif Lindholm
2019-10-09 12:53 ` [edk2-devel] " Philippe Mathieu-Daudé
2019-10-09 13:16 ` Leif Lindholm
2019-10-09 13:36 ` Philippe Mathieu-Daudé
2019-10-09 12:00 ` [PATCH edk2-platforms 3/6] Maintainers.txt: revamp file to machine-readable format Leif Lindholm
2019-10-09 12:31 ` Ard Biesheuvel
2019-10-09 12:47 ` Leif Lindholm
2019-10-09 13:48 ` [edk2-devel] " Liming Gao
2019-10-09 14:27 ` Leif Lindholm
2019-10-09 12:00 ` [PATCH edk2-platforms 4/6] Maintainers.txt: merge Marvell platforms and silicon sections Leif Lindholm
2019-10-09 12:56 ` [edk2-devel] " Philippe Mathieu-Daudé
2019-10-09 13:21 ` Marcin Wojtas
2019-10-09 12:00 ` [PATCH edk2-platforms 5/6] Maintainers.txt: create explicit sections for remaining modules Leif Lindholm
2019-10-09 12:57 ` [edk2-devel] " Philippe Mathieu-Daudé
2019-10-09 12:00 ` [PATCH edk2-platforms 6/6] Maintainers.txt: drop Ard from default section Leif Lindholm
2019-10-09 12:32 ` [PATCH edk2-platforms 0/6] Update Maintainers.txt Ard Biesheuvel
2019-10-09 12:46 ` 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=20191009120013.28076-2-leif.lindholm@linaro.org \
--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