diff options
author | Lei YU <yulei.sh@bytedance.com> | 2020-06-17 09:42:13 +0300 |
---|---|---|
committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | 2020-08-17 22:41:28 +0300 |
commit | 30fb83326eeaad6222e8cce7de45997918605747 (patch) | |
tree | 31b0a49f6c6856db871b2b2feb0b4b543160cffc | |
parent | 1a920f32732eb625144ccbd20048613101cb9dcc (diff) | |
download | openbmc-30fb83326eeaad6222e8cce7de45997918605747.tar.xz |
Add MAINTAINERS
(From meta-bytedance rev: 193994c9c7d389a108808dc55a47cdb715451172)
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: I24d489822b73be76ef64125cd7e71d6771fdb903
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
-rw-r--r-- | meta-bytedance/MAINTAINERS | 46 |
1 files changed, 46 insertions, 0 deletions
diff --git a/meta-bytedance/MAINTAINERS b/meta-bytedance/MAINTAINERS new file mode 100644 index 000000000..c5f155be1 --- /dev/null +++ b/meta-bytedance/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: Lei YU <yulei.sh@bytedance.com> <LeiYU!> +R: Lotus Xu <xuxiaohan@bytedance.com> |