From: Max Filippov <jcmvbkbc@gmail.com>
To: Nick Clifton <nickc@redhat.com>
Cc: "augustine.sterling@gmail.com" <augustine.sterling@gmail.com>,
Binutils <binutils@sourceware.org>
Subject: Re: Transitioning to a new Xtensa port maintainer
Date: Wed, 3 Jun 2020 12:33:05 -0700 [thread overview]
Message-ID: <CAMo8Bf+HwpRicJ2SYFPMCZdHjvcjg7J=xWbfm6YudU9XRvRM=w@mail.gmail.com> (raw)
In-Reply-To: <be22daa1-ef0d-5e11-8288-96f9225b284e@redhat.com>
Hi Nick,
On Wed, Jun 3, 2020 at 3:38 AM Nick Clifton <nickc@redhat.com> wrote:
> If Max is happy with taking up this role, then it is fine with me.
Of course, thanks.
> Max - please could you file and apply a pre-approved commit to add your
> name to the binutils/MAINTAINERS list.
I've done that a while ago:
https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=ab7ad28739a85312b752ea6cf91ce08199d4ab64
in response to the following message from Alan Modra:
https://gcc.gnu.org/pipermail/gcc/2020-May/232669.html
--
Thanks.
-- Max
prev parent reply other threads:[~2020-06-03 19:33 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
2020-06-03 19:33 ` Max Filippov [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='CAMo8Bf+HwpRicJ2SYFPMCZdHjvcjg7J=xWbfm6YudU9XRvRM=w@mail.gmail.com' \
--to=jcmvbkbc@gmail.com \
--cc=augustine.sterling@gmail.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.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).