From: James Greenhalgh <james.greenhalgh@arm.com>
To: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
Cc: "overseers@gcc.gnu.org" <overseers@gcc.gnu.org>
Subject: Re: Write access to GCC repository
Date: Tue, 26 Jan 2016 15:23:00 -0000 [thread overview]
Message-ID: <20160126152312.GA31072@arm.com> (raw)
In-Reply-To: <AM3PR08MB0088FF1A81CAF162EB9076E783D80@AM3PR08MB0088.eurprd08.prod.outlook.com>
On Tue, Jan 26, 2016 at 03:10:09PM +0000, Wilco Dijkstra wrote:
> Hi,
>
> Having submitted a fair number of patches to GCC, I would like to apply for
> write access with James Greenhalgh (AArch64 reviewer) as my sponsor.
I believe you already have sourceware.org access as wilco@sourceware.org
with commit rights for glibc, so there should be no need for a new key.
I'm happy to act as a sponsor for Wilco's commit rights for GCC. This page
https://www.gnu.org/software/gcc/svnwrite.html#policies suggests that's OK
for a reviewer to do. If not, we should be able to find a maintainer who
can sponsor instead.
Thanks,
James Greenhalgh
next parent reply other threads:[~2016-01-26 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AM3PR08MB0088FF1A81CAF162EB9076E783D80@AM3PR08MB0088.eurprd08.prod.outlook.com>
2016-01-26 15:23 ` James Greenhalgh [this message]
2016-01-26 16:20 ` Frank Ch. Eigler
2008-04-18 13:52 Write access to gcc repository Kris Van Hees
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=20160126152312.GA31072@arm.com \
--to=james.greenhalgh@arm.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=overseers@gcc.gnu.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).