From: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
To: "nickc@redhat.com" <nickc@redhat.com>,
Ramana Radhakrishnan <Ramana.Radhakrishnan@arm.com>,
overseers@sourceware.org
Cc: Matthew Malcomson <Matthew.Malcomson@arm.com>
Subject: Write-after privs for Matthew
Date: Wed, 08 May 2019 13:59:00 -0000 [thread overview]
Message-ID: <300fc685-4379-134e-d716-65de3c4c4a12@arm.com> (raw)
Nick,
I think we should give Matthew Malcomson write-after approval for
binutils (he already has an account for GCC), and I've discussed this
f2f with Ramana.
Overseers, subject to nick agreeing the above can you adjust his account
please (matmal01@gcc.gnu.org).
R.
next reply other threads:[~2019-05-08 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 13:59 Richard Earnshaw (lists) [this message]
2019-05-08 14:08 ` Nick Clifton
2019-05-08 14:20 ` Frank Ch. Eigler
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=300fc685-4379-134e-d716-65de3c4c4a12@arm.com \
--to=richard.earnshaw@arm.com \
--cc=Matthew.Malcomson@arm.com \
--cc=Ramana.Radhakrishnan@arm.com \
--cc=nickc@redhat.com \
--cc=overseers@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).