From: Ryan Coe <bluemrp9@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] DEVELOPERS: remove Ryan Coe
Date: Sun, 25 Oct 2020 10:40:28 -0700 [thread overview]
Message-ID: <20201025174028.141027-1-bluemrp9@gmail.com> (raw)
Signed-off-by: Ryan Coe <bluemrp9@gmail.com>
---
DEVELOPERS | 5 -----
1 file changed, 5 deletions(-)
diff --git a/DEVELOPERS b/DEVELOPERS
index 123ffbf033..e9dfe96206 100644
--- a/DEVELOPERS
+++ b/DEVELOPERS
@@ -2288,11 +2288,6 @@ F: package/python-tornado/
F: package/resiprocate/
F: package/websocketpp/
-N: Ryan Coe <bluemrp9@gmail.com>
-F: package/inadyn/
-F: package/libite/
-F: package/mariadb/
-
N: Ryan Wilkins <ryan@deadfrog.net>
F: package/biosdevname/
--
2.25.1
next reply other threads:[~2020-10-25 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-25 17:40 Ryan Coe [this message]
2020-10-26 7:17 ` [Buildroot] [PATCH 1/1] DEVELOPERS: remove Ryan Coe Yann E. MORIN
2020-10-30 8:42 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201025174028.141027-1-bluemrp9@gmail.com \
--to=bluemrp9@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox