diff options
author | Supreeth Venkatesh <supreeth.venkatesh@amd.com> | 2020-11-14 00:46:11 +0300 |
---|---|---|
committer | Andrew Geissler <geissonator@yahoo.com> | 2020-11-17 04:08:08 +0300 |
commit | 6564a664d81023dd43a0d0616355cae6353c9721 (patch) | |
tree | 951fdbf340046c76fbf0bb6475778e3c9334feaf /meta-amd | |
parent | 72c03d7eb7b4c177cb4e480c7b029de739297b08 (diff) | |
download | openbmc-6564a664d81023dd43a0d0616355cae6353c9721.tar.xz |
meta-amd: Add MAINTAINERS file
Adds MAINTAINERS file which lists the initial maintainer for the
meta-amd repository.
(From meta-amd rev: bf95777b8150cef8772d825124b9d72c5a727e9e)
Signed-off-by: Supreeth Venkatesh <supreeth.venkatesh@amd.com>
Change-Id: I498ecb9403c2c4cbfea3a0b4a2e1113fdf244d64
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Diffstat (limited to 'meta-amd')
-rw-r--r-- | meta-amd/MAINTAINERS | 45 |
1 files changed, 45 insertions, 0 deletions
diff --git a/meta-amd/MAINTAINERS b/meta-amd/MAINTAINERS new file mode 100644 index 000000000..a46f429d1 --- /dev/null +++ b/meta-amd/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: Supreeth Venkatesh <supreeth.venkatesh@amd.com> |