From: Andrew John Hughes <gnu_andrew@member.fsf.org>
To: overseers@gcc.gnu.org
Cc: mark@klomp.org
Subject: Request for GCC Write Access
Date: Thu, 29 Jun 2006 19:42:00 -0000 [thread overview]
Message-ID: <1151610170.7451.241.camel@localhost.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 885 bytes --]
Hi,
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.
Thanks,
--
Andrew :-)
Please avoid sending me Microsoft Office (e.g. Word, PowerPoint)
attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html
If you use Microsoft Office, support movement towards the end of vendor
lock-in:
http://opendocumentfellowship.org/petition/
"Value your freedom, or you will lose it, teaches history.
`Don't bother us with politics' respond those who don't want to learn."
-- Richard Stallman
Escape the Java Trap with GNU Classpath!
http://www.gnu.org/philosophy/java-trap.html
public class gcj extends Freedom implements Java { ... }
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2006-06-29 19:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 19:42 Andrew John Hughes [this message]
[not found] ` <20060629194804.GE913@redhat.com>
2006-06-29 20:41 ` Andrew John Hughes
2006-06-29 23:35 ` Christopher Faylor
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=1151610170.7451.241.camel@localhost.localdomain \
--to=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).