public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Joel Sherrill <joel@rtems.org>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>,
	"newlib@sourceware.org" <newlib@sourceware.org>
Subject: Re: [PATCH] Add OS Port Maintainers to newlib/MAINTAINERS
Date: Wed, 07 Jun 2017 15:59:00 -0000	[thread overview]
Message-ID: <d02aa81e-6a43-568b-701c-fb8f9403461a@rtems.org> (raw)
In-Reply-To: <20170607125630.16154-1-sebastian.huber@embedded-brains.de>

joel@oarcorp.com turned into a spam magnet. :(

joel.sherrill@oarcorp.com is the proper email now.

--joel

On 6/7/2017 7:56 AM, Sebastian Huber wrote:
> ---
>   newlib/MAINTAINERS | 9 +++++++++
>   1 file changed, 9 insertions(+)
> 
> diff --git a/newlib/MAINTAINERS b/newlib/MAINTAINERS
> index 6117ff4a9..74500a251 100644
> --- a/newlib/MAINTAINERS
> +++ b/newlib/MAINTAINERS
> @@ -46,6 +46,15 @@ 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@oarcorp.com
> +rtems			Sebastian Huber		sebastian.huber@embedded-brains.de
> +
> +
>   			Write After Approval
>   
>   These are users with general write privileges after getting approval:
> 

-- 
Joel Sherrill, Ph.D.
Check out RTEMS at https://www.rtems.org
Truly free real-time operating sysem

      reply	other threads:[~2017-06-07 15:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-07 12:56 Sebastian Huber
2017-06-07 15:59 ` Joel Sherrill [this message]

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=d02aa81e-6a43-568b-701c-fb8f9403461a@rtems.org \
    --to=joel@rtems.org \
    --cc=newlib@sourceware.org \
    --cc=sebastian.huber@embedded-brains.de \
    /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).