From: Mark Wielaard <mark@klomp.org>
To: Richard Ball via Overseers <overseers@sourceware.org>
Cc: "overseers@gcc.gnu.org" <overseers@gcc.gnu.org>,
Richard Ball <Richard.Ball@arm.com>,
Richard Sandiford <Richard.Sandiford@arm.com>
Subject: Re: Binutils write access
Date: Thu, 10 Aug 2023 00:34:14 +0200 [thread overview]
Message-ID: <20230809223414.GP12836@gnu.wildebeest.org> (raw)
In-Reply-To: <DB9PR08MB69575A489B18D13037D553948112A@DB9PR08MB6957.eurprd08.prod.outlook.com>
Hi Richard,
Please use admin-requests@sourceware.org instead of overseers next
time, it is a private list specifically for account issues.
On Wed, Aug 09, 2023 at 04:21:21PM +0000, Richard Ball via Overseers wrote:
> Could I please have my write access for account
> ricbal02@sourceware.org extended to include Binutils write access?
>
> Sponsor is Richard Sandiford richard.sandiford@arm.com
You have been added to the src group (for binutils-gdb) and you now
have Write After Approval for binutils. Please check
binutils/MAINTAINERS for commit rules.
Cheers,
Mark
next prev parent reply other threads:[~2023-08-09 22:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 16:21 Richard Ball
2023-08-09 22:34 ` Mark Wielaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-26 5:37 Stefan Schulze Frielinghaus
2020-05-26 14:50 ` Christopher Faylor
2020-05-26 15:35 ` Stefan Schulze Frielinghaus
2020-05-18 19:12 Stefan Schulze Frielinghaus
2020-05-18 19:59 ` Christopher Faylor
2017-05-15 13:23 Adhemerval Zanella
2017-05-15 14:48 ` Maxim Kuvyrkov
2017-05-16 14:42 ` Frank Ch. Eigler
2016-03-08 1:14 binutils " Trevor Saunders
2016-03-08 1:48 ` Frank Ch. Eigler
2015-07-24 7:56 Binutils " Robert Suchanek
2015-07-25 0:20 ` Ian Lance Taylor
[not found] <1423917696.18129.45.camel@yam-132-YW-E178-FTW>
[not found] ` <20150214.220943.231145352.kkojima@rr.iij4u.or.jp>
[not found] ` <1423919554.18129.47.camel@yam-132-YW-E178-FTW>
[not found] ` <20150214.224141.334659530.kkojima@rr.iij4u.or.jp>
[not found] ` <54EB61FC.4000607@redhat.com>
[not found] ` <1424729272.14981.364.camel@yam-132-YW-E178-FTW>
[not found] ` <54EC466B.5060902@redhat.com>
2015-02-24 10:14 ` binutils " Oleg Endo
2015-02-25 13:14 ` Ian Lance Taylor
2011-11-29 19:49 Andrew Pinski
2011-11-29 20:06 ` Christopher Faylor
2000-12-30 6:08 Ulrich Drepper
2000-04-04 13:38 ` Ulrich Drepper
2000-12-30 6:08 ` Ian Lance Taylor
2000-04-04 13:45 ` Ian Lance Taylor
2000-12-30 6:08 ` Ulrich Drepper
2000-04-04 13:59 ` Ulrich Drepper
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=20230809223414.GP12836@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=Richard.Ball@arm.com \
--cc=Richard.Sandiford@arm.com \
--cc=overseers@gcc.gnu.org \
--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).