diff options
author | Brad Bishop <bradleyb@fuzziesquirrel.com> | 2018-06-21 17:32:34 +0300 |
---|---|---|
committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | 2018-06-26 15:47:12 +0300 |
commit | b49986afd2b95c63a17a6d7e8cae3251ab300e71 (patch) | |
tree | c693738fa97d3cf7847e3eb93fbb612873408be9 /meta-openbmc-machines | |
parent | 3381c782f55c109e859188305262ed4c3ac85311 (diff) | |
download | openbmc-b49986afd2b95c63a17a6d7e8cae3251ab300e71.tar.xz |
Add meta-openpower subtree maintainers file
Change-Id: I64ad8377d1aceb0949a48a11ba69825f59ae1f69
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Diffstat (limited to 'meta-openbmc-machines')
-rw-r--r-- | meta-openbmc-machines/meta-openpower/MAINTAINERS | 48 |
1 files changed, 48 insertions, 0 deletions
diff --git a/meta-openbmc-machines/meta-openpower/MAINTAINERS b/meta-openbmc-machines/meta-openpower/MAINTAINERS new file mode 100644 index 000000000..9b799c237 --- /dev/null +++ b/meta-openbmc-machines/meta-openpower/MAINTAINERS @@ -0,0 +1,48 @@ +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 +------------------------- + +# THIS REPOSITORY HAS A DIFFERENT SUBMISSION PROCESS: this is a subtree in +# @openbmc and is synced by the maintainer using git-subtree. Please submit +# changes against @openbmc. +M: Brad Bishop <bradleyb@fuzziesquirrel.com> <radsquirrel!> |