1*8bc8ba8eSkasunathHow to use this list: 2*8bc8ba8eSkasunath Find the most specific section entry (described below) that matches where 3*8bc8ba8eSkasunath your change lives and add the reviewers (R) and maintainers (M) as 4*8bc8ba8eSkasunath reviewers. You can use the same method to track down who knows a particular 5*8bc8ba8eSkasunath code base best. 6*8bc8ba8eSkasunath 7*8bc8ba8eSkasunath Your change/query may span multiple entries; that is okay. 8*8bc8ba8eSkasunath 9*8bc8ba8eSkasunath If you do not find an entry that describes your request at all, someone 10*8bc8ba8eSkasunath forgot to update this list; please at least file an issue or send an email 11*8bc8ba8eSkasunath to a maintainer, but preferably you should just update this document. 12*8bc8ba8eSkasunath 13*8bc8ba8eSkasunathDescription of section entries: 14*8bc8ba8eSkasunath 15*8bc8ba8eSkasunath Section entries are structured according to the following scheme: 16*8bc8ba8eSkasunath 17*8bc8ba8eSkasunath X: NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!> 18*8bc8ba8eSkasunath X: ... 19*8bc8ba8eSkasunath . 20*8bc8ba8eSkasunath . 21*8bc8ba8eSkasunath . 22*8bc8ba8eSkasunath 23*8bc8ba8eSkasunath Where REPO_NAME is the name of the repository within the OpenBMC GitHub 24*8bc8ba8eSkasunath organization; FILE_PATH is a file path within the repository, possibly with 25*8bc8ba8eSkasunath wildcards; X is a tag of one of the following types: 26*8bc8ba8eSkasunath 27*8bc8ba8eSkasunath M: Denotes maintainer; has fields NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>; 28*8bc8ba8eSkasunath if omitted from an entry, assume one of the maintainers from the 29*8bc8ba8eSkasunath MAINTAINERS entry. 30*8bc8ba8eSkasunath R: Denotes reviewer; has fields NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>; 31*8bc8ba8eSkasunath these people are to be added as reviewers for a change matching the repo 32*8bc8ba8eSkasunath path. 33*8bc8ba8eSkasunath F: Denotes forked from an external repository; has fields URL. 34*8bc8ba8eSkasunath 35*8bc8ba8eSkasunath Line comments are to be denoted "# SOME COMMENT" (typical shell style 36*8bc8ba8eSkasunath comment); it is important to follow the correct syntax and semantics as we 37*8bc8ba8eSkasunath may want to use automated tools with this file in the future. 38*8bc8ba8eSkasunath 39*8bc8ba8eSkasunath A change cannot be added to an OpenBMC repository without a MAINTAINER's 40*8bc8ba8eSkasunath approval; thus, a MAINTAINER should always be listed as a reviewer. 41*8bc8ba8eSkasunath 42*8bc8ba8eSkasunathSTART OF MAINTAINERS LIST 43*8bc8ba8eSkasunath------------------------- 44*8bc8ba8eSkasunath 45*8bc8ba8eSkasunathM: Brandon Kim <brandonkim@google.com> <brandonk!> 46*8bc8ba8eSkasunathM: Ed Tanous <ed@tanous.net> <edtanous!> 47*8bc8ba8eSkasunathM: Willy Tu <wltu@google.com> <wltu!> 48*8bc8ba8eSkasunathR: Kasun Athukorala <kasunath@google.com> <kasunath!> 49