From: Shujing Zhao <pearly.zhao@oracle.com>
To: overseers@sourceware.org
Cc: Ian Lance Taylor <iant@google.com>
Subject: Re: Request write access to gcc
Date: Mon, 07 Dec 2009 11:02:00 -0000 [thread overview]
Message-ID: <4B1CE02B.3040803@oracle.com> (raw)
In-Reply-To: <m3skbrwamf.fsf@pepe.airs.com>
On 12/04/2009 01:50 PM, Ian Lance Taylor wrote:
>
> I have replaced your old SSH key with the one you sent, and added you to
> the gcc group.
>
I'm very sorry to cause you this trouble again.
I have messed the public and write-enabled trees and got in trouble with commit.
The old private key is cover incautiously when I try to solve the commit problem.
Can you replace my old SSH key with this one again?
ssh-dss
AAAAB3NzaC1kc3MAAACBAPV14UHFwNa4QpTM+PMsEMFrTSkpZMg9ILqf6sAMSJrfgOs9oMfeGknL96K3aYMQMlq5/akf5IwpkWWLPMG5ikvPkPZjJFqo3LaJnxI/LCmfkWHUl1gZGtSlwrmgcCwwAvICOfPLC0RxbQL48LDZuTLLaUtmmWrXdTGg+jsI6N+1AAAAFQCSnWsEPZKwWtScx2NMAF0EILDbvQAAAIEAhPJKVXoy7MrBCmGMWV6ciTjOfOeHc398wkq7wV8vRbwW54qXUKc3lgv7yZGo2lb48n+ryvmxYuqtvOsQOR/8ul1iFgnxv5JjQNqTyOWG1SR2qvsVzDdxj1j2dVA58PczSdu+IfXhcYYdHtNl1A5GQPkwCNxmPBQ4KZirfCEmN90AAACBAOEIVnD/7ieu8nLkvLFiU1U8Z4tzxFYOzN5qFs4ZUkMj+N7NuyowTpAOjRJqzXiTaERqmXYwL36H2l1Sl1aliZ8mw9x8l+lPfi1U6BGg++F47h7V/rqMITlmjn3OP9BKvRXdZvhEkLpHxkp0cLaebKbQL6vvnJcgKst3RhX5CJv+
pzhao@zhao
Sorry
Pearly
next prev parent reply other threads:[~2009-12-07 11:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 1:49 Shujing Zhao
2009-12-04 5:51 ` Ian Lance Taylor
2009-12-07 11:02 ` Shujing Zhao [this message]
2009-12-07 18:34 ` Ian Lance Taylor
2015-05-15 21:04 Request write access to GCC James Bowman
2015-05-16 4:35 ` 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=4B1CE02B.3040803@oracle.com \
--to=pearly.zhao@oracle.com \
--cc=iant@google.com \
--cc=overseers@sourceware.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).