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