From: Nick Clifton <nickc@redhat.com>
To: "augustine.sterling@gmail.com" <augustine.sterling@gmail.com>,
Max Filippov <jcmvbkbc@gmail.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: Transitioning to a new Xtensa port maintainer
Date: Wed, 3 Jun 2020 11:38:25 +0100 [thread overview]
Message-ID: <be22daa1-ef0d-5e11-8288-96f9225b284e@redhat.com> (raw)
In-Reply-To: <CAGSvup9+vxhY42GtCzRzYopakQRj0m0S7xQqnWKuS0cjqBKMaA@mail.gmail.com>
Hi Sterling, Hi Max,
On 2020-05-28 18:12, augustine.sterling--- via Binutils wrote:
> After a long run as the Xtensa port maintainer, it is time for me to move
> on.
Thank you very much for your time and effort in this role.
> I nominate Max Filippov [cc'd] as the new maintainer. He has contributed
> numerous patches over the years which have required minimal comments from
> me.
If Max is happy with taking up this role, then it is fine with me.
> If there is anything I need to do to facilitate this, let me know. I'm
> happy to still review patches when needed.
OK, so Sterling - please could you file and apply a pre-approved patch to
remove your name from the binutils/MAINTAINERS list.
Max - please could you file and apply a pre-approved commit to add your
name to the binutils/MAINTAINERS list.
Cheers
Nick
PS. Just to be clear I am talking about the MAINTAINERS file inside
the binutils/ subdirectory of the binutils sources, not the MAINTAINERS
file at the top level of the binutils sources.
next prev parent reply other threads:[~2020-06-03 10:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 17:12 augustine.sterling
2020-06-03 10:38 ` Nick Clifton [this message]
2020-06-03 19:33 ` Max Filippov
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=be22daa1-ef0d-5e11-8288-96f9225b284e@redhat.com \
--to=nickc@redhat.com \
--cc=augustine.sterling@gmail.com \
--cc=binutils@sourceware.org \
--cc=jcmvbkbc@gmail.com \
/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).