public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
* Re: Write access to GCC repository
       [not found] <AM3PR08MB0088FF1A81CAF162EB9076E783D80@AM3PR08MB0088.eurprd08.prod.outlook.com>
@ 2016-01-26 15:23 ` James Greenhalgh
  2016-01-26 16:20   ` Frank Ch. Eigler
  0 siblings, 1 reply; 3+ messages in thread
From: James Greenhalgh @ 2016-01-26 15:23 UTC (permalink / raw)
  To: Wilco Dijkstra; +Cc: overseers

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Write access to GCC repository
  2016-01-26 15:23 ` Write access to GCC repository James Greenhalgh
@ 2016-01-26 16:20   ` Frank Ch. Eigler
  0 siblings, 0 replies; 3+ messages in thread
From: Frank Ch. Eigler @ 2016-01-26 16:20 UTC (permalink / raw)
  To: James Greenhalgh; +Cc: Wilco Dijkstra, overseers

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.

Done.

- FChE

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Write access to gcc repository
@ 2008-04-18 13:52 Kris Van Hees
  0 siblings, 0 replies; 3+ messages in thread
From: Kris Van Hees @ 2008-04-18 13:52 UTC (permalink / raw)
  To: overseers

Hi, I'd like to request write access to the gcc project, per suggestion from
Jason Merrill <jason@redhat.com>.  I already have an account on sourceware.org,
under the login 'kvanhees'.

	Cheers,
	Kris

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2016-01-26 16:20 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <AM3PR08MB0088FF1A81CAF162EB9076E783D80@AM3PR08MB0088.eurprd08.prod.outlook.com>
2016-01-26 15:23 ` Write access to GCC repository James Greenhalgh
2016-01-26 16:20   ` Frank Ch. Eigler
2008-04-18 13:52 Write access to gcc repository Kris Van Hees

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).