From: Ian Lance Taylor <ian@airs.com>
To: "Fang, Changpeng" <Changpeng.Fang@amd.com>
Cc: "overseers@gcc.gnu.org" <overseers@gcc.gnu.org>, cfang.gcc@gmail.com
Subject: Re: request for access to the GCC repository
Date: Wed, 04 Aug 2010 08:26:00 -0000 [thread overview]
Message-ID: <m3tyna7pj0.fsf@pepe.airs.com> (raw)
In-Reply-To: <D4C76825A6780047854A11E93CDE84D00A678D15@SAUSEXMBP01.amd.com> (Changpeng Fang's message of "Tue, 3 Aug 2010 15:22:17 -0500")
"Fang, Changpeng" <Changpeng.Fang@amd.com> writes:
> Hi, I attached in the file. Hopefully it works.
I installed the new SSH key.
Ian
next prev parent reply other threads:[~2010-08-04 8:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 18:58 Fang, Changpeng
2010-08-03 20:20 ` Ian Lance Taylor
2010-08-03 20:23 ` Fang, Changpeng
2010-08-04 8:26 ` Ian Lance Taylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-06 16:58 Request for access to the gcc repository Sterling Augustine
2006-01-31 20:39 request for access to the GCC repository Robert Schuster
2006-01-31 23:21 ` Tom Tromey
2006-01-31 20:35 Robert Schuster
2005-07-28 13:43 Request " Maciej W. Rozycki
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=m3tyna7pj0.fsf@pepe.airs.com \
--to=ian@airs.com \
--cc=Changpeng.Fang@amd.com \
--cc=cfang.gcc@gmail.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).