From: Andrew John Hughes <gnu_andrew@member.fsf.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: mark@klomp.org, overseers@gcc.gnu.org
Subject: Re: Request for GCC Write Access
Date: Thu, 29 Jun 2006 20:41:00 -0000 [thread overview]
Message-ID: <1151613618.7451.252.camel@localhost.localdomain> (raw)
In-Reply-To: <20060629194804.GE913@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 874 bytes --]
On Thu, 2006-06-29 at 15:48 -0400, Frank Ch. Eigler wrote:
> Hi -
>
> Please use the "request cvs write access" form on the web site,
> which will ask you to include an ssh public key for authentication.
>
> - FChE
According to the web site,
'If you already have an account on sourceware.org, please send email to
overseers(at)gcc.gnu.org with a request for access to the GCC
repository. Include the name of the person who is sponsoring your access
and CC: your email to them. Else use this form to supply your SSH public
key (which you can generate via the ssh-keygen program) and other
details.'
I already have an account on sourceware.org, so I'm complying with those
requirements.
--
Andrew :-)
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 prev parent reply other threads:[~2006-06-29 20:41 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 [this message]
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=1151613618.7451.252.camel@localhost.localdomain \
--to=gnu_andrew@member.fsf.org \
--cc=fche@redhat.com \
--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).