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