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