From: Christopher Faylor <me@cgf.cx>
To: overseers@gcc.gnu.org,
Andrew John Hughes <gnu_andrew@member.fsf.org>,
mark@klomp.org
Subject: Re: Request for GCC Write Access
Date: Thu, 29 Jun 2006 23:35:00 -0000 [thread overview]
Message-ID: <20060629233535.GA31683@trixie.casa.cgf.cx> (raw)
In-Reply-To: <1151610170.7451.241.camel@localhost.localdomain>
On Thu, Jun 29, 2006 at 08:42:50PM +0100, Andrew John Hughes wrote:
>I'll be making some contributions to GCC, initially as part of
>my Google SoC project. My assignment just went through with the
>FSF. I already have a sourceware account as part of my use of
>the Mauve project (username is gandalf). Mark Wielaard sponsors
>my access.
I've added you to the gcc group.
cgf
next prev parent reply other threads:[~2006-06-29 23:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 19:42 Andrew John Hughes
[not found] ` <20060629194804.GE913@redhat.com>
2006-06-29 20:41 ` Andrew John Hughes
2006-06-29 23:35 ` Christopher Faylor [this message]
2011-01-16 7:46 request for gcc write access Mike Frysinger
2011-01-16 7:53 ` Jie Zhang
2011-01-17 23:56 ` Ian Lance Taylor
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=20060629233535.GA31683@trixie.casa.cgf.cx \
--to=me@cgf.cx \
--cc=gnu_andrew@member.fsf.org \
--cc=mark@klomp.org \
--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).