diff options
author | Patrick Williams <patrick@stwcx.xyz> | 2020-11-17 16:23:18 +0300 |
---|---|---|
committer | Andrew Geissler <geissonator@yahoo.com> | 2020-11-17 16:39:12 +0300 |
commit | 8075ec32f3ff14d94511d8082f6d3e591a21eb38 (patch) | |
tree | 0bc3ba2715a2aff520c87e76f94d83c913b77868 /meta-portwell | |
parent | 435392e47badb5570c8364a885eafdb453f8f033 (diff) | |
download | openbmc-8075ec32f3ff14d94511d8082f6d3e591a21eb38.tar.xz |
MAINTAINERS: add file
(From meta-portwell rev: 1a8c063c5b490a3d031e5b1c2c403479d22ce3fb)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ib8180763df3175e4871241b53c39ce42871ed87c
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Diffstat (limited to 'meta-portwell')
-rw-r--r-- | meta-portwell/MAINTAINERS | 46 |
1 files changed, 46 insertions, 0 deletions
diff --git a/meta-portwell/MAINTAINERS b/meta-portwell/MAINTAINERS new file mode 100644 index 0000000000..a27fe90359 --- /dev/null +++ b/meta-portwell/MAINTAINERS @@ -0,0 +1,46 @@ +How to use this list: + Find the most specific section entry (described below) that matches where + your change lives and add the reviewers (R) and maintainers (M) as + reviewers. You can use the same method to track down who knows a particular + code base best. + + Your change/query may span multiple entries; that is okay. + + If you do not find an entry that describes your request at all, someone + forgot to update this list; please at least file an issue or send an email + to a maintainer, but preferably you should just update this document. + +Description of section entries: + + Section entries are structured according to the following scheme: + + X: NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!> + X: ... + . + . + . + + Where REPO_NAME is the name of the repository within the OpenBMC GitHub + organization; FILE_PATH is a file path within the repository, possibly with + wildcards; X is a tag of one of the following types: + + M: Denotes maintainer; has fields NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>; + if omitted from an entry, assume one of the maintainers from the + MAINTAINERS entry. + R: Denotes reviewer; has fields NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>; + these people are to be added as reviewers for a change matching the repo + path. + F: Denotes forked from an external repository; has fields URL. + + Line comments are to be denoted "# SOME COMMENT" (typical shell style + comment); it is important to follow the correct syntax and semantics as we + may want to use automated tools with this file in the future. + + A change cannot be added to an OpenBMC repository without a MAINTAINER's + approval; thus, a MAINTAINER should always be listed as a reviewer. + +START OF MAINTAINERS LIST +------------------------- + +M: Amithash Prasad <amithash@fb.com> +M: Patrick Williams <patrick@stwcx.xyz> <stwcx!> |