diff options
author | John Wang <wangzqbj@inspur.com> | 2019-05-31 11:11:56 +0300 |
---|---|---|
committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | 2019-06-05 15:58:45 +0300 |
commit | 586584d50487ea70777ad0c8b906ea4c9c6df42e (patch) | |
tree | 17b762cbdb2c83fe5d4ad6b8ba2cc061cfd96e83 /meta-inspur | |
parent | 988b28b864d09591032b145b278f5f30ceb97c16 (diff) | |
download | openbmc-586584d50487ea70777ad0c8b906ea4c9c6df42e.tar.xz |
meta-inspur: Add MAINTAINERS file
(From meta-inspur rev: 072b7d4889bce9c967bbde393334bd63e13052bd)
Signed-off-by: John Wang <wangzqbj@inspur.com>
Change-Id: I93cdd9470db20ebc800aaf5ece95721d295b8f9c
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Diffstat (limited to 'meta-inspur')
-rw-r--r-- | meta-inspur/MAINTAINERS | 47 |
1 files changed, 47 insertions, 0 deletions
diff --git a/meta-inspur/MAINTAINERS b/meta-inspur/MAINTAINERS new file mode 100644 index 0000000000..af86b18f7e --- /dev/null +++ b/meta-inspur/MAINTAINERS @@ -0,0 +1,47 @@ +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: John Wang <wangzqbj@inspur.com> <JohnWang!> +R: George Liu <liuxiwei@inspur.com> <liuxiwei!> +R: Lei Yu <mine260309@gmail.com> <LeiYU!> |