diff options
author | Brad Bishop <bradleyb@fuzziesquirrel.com> | 2019-11-11 22:06:29 +0300 |
---|---|---|
committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | 2019-11-12 19:51:10 +0300 |
commit | f8df153328c17d4a333ab1315dd3c42c0fb1ec34 (patch) | |
tree | 84fece4b4d322d35d9723f3feb594029200f8539 /meta-nuvoton/MAINTAINERS | |
parent | 6f6bd10f898f3a78c01a22508a5f3b9e444db32e (diff) | |
download | openbmc-f8df153328c17d4a333ab1315dd3c42c0fb1ec34.tar.xz |
nuvoton: Add MAINTAINERS
Add a maintainers file for meta-nuvoton. Benjamin is commit count
leader and he already does high quality reviews of all the meta-nuvoton
patches.
(From meta-nuvoton rev: 75e2474d1f6d227e2d53a4bc1773ee928542d84f)
Change-Id: I9deb71187866841d37965610a31c7730d45d9b9f
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Diffstat (limited to 'meta-nuvoton/MAINTAINERS')
-rw-r--r-- | meta-nuvoton/MAINTAINERS | 45 |
1 files changed, 45 insertions, 0 deletions
diff --git a/meta-nuvoton/MAINTAINERS b/meta-nuvoton/MAINTAINERS new file mode 100644 index 0000000000..3bc2ef64bd --- /dev/null +++ b/meta-nuvoton/MAINTAINERS @@ -0,0 +1,45 @@ +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: Benjamin Fair <benjaminfair@google.com> <benjaminfair!> |