diff options
author | Patrick Venture <venture@google.com> | 2019-03-05 13:26:27 -0800 |
---|---|---|
committer | Patrick Venture <venture@google.com> | 2019-03-05 13:30:48 -0800 |
commit | 85e320906546f3e5a0dfe1ab54a826517dae2a0d (patch) | |
tree | 3f146794cb43e3260ff5cd54015b937a91a4b814 | |
parent | b4433985d6b8d50dd56cf5802634d726c160de49 (diff) | |
download | ipmi-blob-tool-85e320906546f3e5a0dfe1ab54a826517dae2a0d.tar.gz ipmi-blob-tool-85e320906546f3e5a0dfe1ab54a826517dae2a0d.zip |
Add MAINTAINERS file
Add MAINTAINERS file with one maintainer entry.
Change-Id: I987f50299f41111bc1f4e6b4073797cac9a732c1
Signed-off-by: Patrick Venture <venture@google.com>
-rw-r--r-- | MAINTAINERS | 45 |
1 files changed, 45 insertions, 0 deletions
diff --git a/MAINTAINERS b/MAINTAINERS new file mode 100644 index 0000000..b918af2 --- /dev/null +++ b/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: Patrick Venture <venture@google.com> <venture!> |