summaryrefslogtreecommitdiff
path: root/meta-hxt/MAINTAINERS
diff options
context:
space:
mode:
authorPatrick Williams <patrick@stwcx.xyz>2021-10-13 04:28:34 +0300
committerPatrick Williams <patrick@stwcx.xyz>2021-10-22 21:46:04 +0300
commit957bbed0f6dd76578dbf1d242e608cf7397982f6 (patch)
tree6e4966ed93615096677b95a5212662bcb52cf4e5 /meta-hxt/MAINTAINERS
parent6323cb3a4251c37d8ac2aabf9afc1dc22740c8a6 (diff)
downloadopenbmc-957bbed0f6dd76578dbf1d242e608cf7397982f6.tar.xz
meta-hxt: remove unusable stardragon4800-rep2 machine
This machine is unbuildable and has not been updated in the requisite 2 months per https://lore.kernel.org/openbmc/YRUW7cazmCjW8VpP@heinlein/, so it is being deleted. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ie0d34a9c3146c60c5543e00a48f33aeb56ab419d
Diffstat (limited to 'meta-hxt/MAINTAINERS')
-rw-r--r--meta-hxt/MAINTAINERS47
1 files changed, 0 insertions, 47 deletions
diff --git a/meta-hxt/MAINTAINERS b/meta-hxt/MAINTAINERS
deleted file mode 100644
index 5a497df660..0000000000
--- a/meta-hxt/MAINTAINERS
+++ /dev/null
@@ -1,47 +0,0 @@
-How to use this list:
- Find the most specific section entry (described below) that matches where
- your change lives and add the reviewers (R) and maintainers (M) as
- reviewers. You can use the same method to track down who knows a particular
- code base best.
-
- Your change/query may span multiple entries; that is okay.
-
- If you do not find an entry that describes your request at all, someone
- forgot to update this list; please at least file an issue or send an email
- to a maintainer, but preferably you should just update this document.
-
-Description of section entries:
-
- Section entries are structured according to the following scheme:
-
- X: NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>
- X: ...
- .
- .
- .
-
- Where REPO_NAME is the name of the repository within the OpenBMC GitHub
- organization; FILE_PATH is a file path within the repository, possibly with
- wildcards; X is a tag of one of the following types:
-
- M: Denotes maintainer; has fields NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>;
- if omitted from an entry, assume one of the maintainers from the
- MAINTAINERS entry.
- R: Denotes reviewer; has fields NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>;
- these people are to be added as reviewers for a change matching the repo
- path.
- F: Denotes forked from an external repository; has fields URL.
-
- Line comments are to be denoted "# SOME COMMENT" (typical shell style
- comment); it is important to follow the correct syntax and semantics as we
- may want to use automated tools with this file in the future.
-
- A change cannot be added to an OpenBMC repository without a MAINTAINER's
- approval; thus, a MAINTAINER should always be listed as a reviewer.
-
-START OF MAINTAINERS LIST
--------------------------
-
-M: Yuan Yao <yao.yuan@hxt-semitech.com> <yyaocs!>
-M: Brad Bishop <bradleyb@fuzziesquirrel.com> <radsquirrel!>
-R: Patrick Venture <venture@google.com> <venture!>