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