From 956853824910b6150387154e5255eb1b9c95a39d Mon Sep 17 00:00:00 2001 From: Patrick Venture Date: Thu, 4 Oct 2018 09:36:18 -0700 Subject: meta-google: add maintainers file Add a maintainers file for the meta-google layer. (From meta-google rev: 91a5446f9f0e176874f585c04261c8beaf1d5ab9) Change-Id: Ifea3727d5b1a86902430482908a4b3bd7a2fab83 Signed-off-by: Patrick Venture Signed-off-by: Brad Bishop --- meta-google/MAINTAINERS | 46 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 46 insertions(+) create mode 100644 meta-google/MAINTAINERS (limited to 'meta-google') diff --git a/meta-google/MAINTAINERS b/meta-google/MAINTAINERS new file mode 100644 index 000000000..f5370daf0 --- /dev/null +++ b/meta-google/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 + 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 ; + if omitted from an entry, assume one of the maintainers from the + MAINTAINERS entry. + R: Denotes reviewer; has fields NAME ; + 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 +M: Nancy Yuen -- cgit v1.2.3