public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Joel Sherrill <joel@rtems.org>
To: newlib@sourceware.org
Cc: Joel Sherrill <joel@rtems.org>
Subject: [PATCH] newlib/MAINTAINERS: Add OS maintainers section and myself for RTEMS and Write After Approval.
Date: Tue, 13 Jun 2017 19:31:00 -0000	[thread overview]
Message-ID: <1497389420-19708-1-git-send-email-joel@rtems.org> (raw)

---
 newlib/MAINTAINERS | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/newlib/MAINTAINERS b/newlib/MAINTAINERS
index 6117ff4..0bd93ff 100644
--- a/newlib/MAINTAINERS
+++ b/newlib/MAINTAINERS
@@ -45,6 +45,12 @@ aarch64			Richard Earnshaw	richard.earnshaw@arm.com
 msp430			DJ Delorie		dj@redhat.com
 			Nick Clifton		nickc@redhat.com
 
+			OS Port Maintainers	(OS alphabetical order)
+
+OS port maintainers may make changes in OS-specific directories, as
+well as OS-specific portions of the build system, without approval.
+
+RTEMS			Joel Sherrill		joel.sherrill@oarcorp.com
 
 			Write After Approval
 
@@ -57,3 +63,4 @@ Nick Clifton			nickc@redhat.com
 Eric Blake			eblake@redhat.com
 Will Newton			will.newton@linaro.org
 Sebastian Huber			sebastian.huber@embedded-brains.de
+Joel Sherrill			joel.sherrill@oarcorp.com
-- 
1.8.3.1

             reply	other threads:[~2017-06-13 19:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13 19:31 Joel Sherrill [this message]
2017-06-14  8:50 ` Corinna Vinschen
2017-06-14 15:49   ` Jeff Johnston
2017-06-14 16:07     ` Joel Sherrill
2017-06-22  8:06     ` Sebastian Huber
2017-10-10 14:36 [PATCH 1/2] newlib/configure.host: Remove obsolete definition of _I386MACH_ALLOW_HW_INTERRUPTS Joel Sherrill
2017-10-10 14:36 ` [PATCH] newlib/MAINTAINERS: Add OS maintainers section and myself for RTEMS and Write After Approval Joel Sherrill
2017-10-11 10:53   ` Joel Sherrill

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=1497389420-19708-1-git-send-email-joel@rtems.org \
    --to=joel@rtems.org \
    --cc=newlib@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).