diff options
author | Brad Bishop <bradleyb@fuzziesquirrel.com> | 2018-06-21 17:32:03 +0300 |
---|---|---|
committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | 2018-06-26 15:46:44 +0300 |
commit | 3381c782f55c109e859188305262ed4c3ac85311 (patch) | |
tree | fa2870f88a9ab9353f06a87c720167d10f12fe91 /meta-openbmc-bsp | |
parent | 0c52342a2c9ab991f167d846b74219fe391accc2 (diff) | |
download | openbmc-3381c782f55c109e859188305262ed4c3ac85311.tar.xz |
Add meta-aspeed subtree maintainers file
Change-Id: I1adc3b6af76cdc37017652f52fa8bbe0d10ac839
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Diffstat (limited to 'meta-openbmc-bsp')
-rw-r--r-- | meta-openbmc-bsp/meta-aspeed/MAINTAINERS | 48 |
1 files changed, 48 insertions, 0 deletions
diff --git a/meta-openbmc-bsp/meta-aspeed/MAINTAINERS b/meta-openbmc-bsp/meta-aspeed/MAINTAINERS new file mode 100644 index 000000000..9b799c237 --- /dev/null +++ b/meta-openbmc-bsp/meta-aspeed/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!> |