public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Fang, Changpeng" <Changpeng.Fang@amd.com>
To: "Fang, Changpeng" <Changpeng.Fang@amd.com>,
	"overseers@sourceware.org" <overseers@sourceware.org>
Subject: RE: update the publickey for gcc acount
Date: Tue, 05 Apr 2011 21:49:00 -0000	[thread overview]
Message-ID: <D4C76825A6780047854A11E93CDE84D004DEB2D22E@SAUSEXMBP01.amd.com> (raw)
In-Reply-To: <D4C76825A6780047854A11E93CDE84D004DEB2D22C@SAUSEXMBP01.amd.com>

[-- Attachment #1: Type: text/plain, Size: 581 bytes --]

Hi,

I upgraded my system, and would you please update my public key on sourceware.org?
I am working on gcc development and my use name is cfang

Thanks,

Changpeng


________________________________________
From: Fang, Changpeng
Sent: Friday, April 01, 2011 4:50 PM
To: overseers@sourceware.org
Subject: update the publickey for gcc acount

Hi,

Would you please update the publickey on sourceware.org.
I could not ssh to sourceware to update it myself.
my username is cfang, and I am working on the gcc project!
The key is attached!

Thanks,

Changpeng

[-- Attachment #2: id_dsa.pub --]
[-- Type: application/octet-stream, Size: 606 bytes --]

ssh-dss AAAAB3NzaC1kc3MAAACBAPcaaUUN4Rzl0La6KTVl6eLNoH+R9lIlrj53PCVEf7CtC0OGufAnHiNqOAwa3ybxVUVWh2KkXR5Ue1re8Kk34+Ed06Wtxvd0Qjy+2jn2AKlAuybuCI2BRKSCMPoxUbefOCMIPtZYpdhRBFYTPiXpIgwkuYno7tO37SC4rf7ViFFVAAAAFQCYOA/y7ysISOz14nG/8Ber4hfKjwAAAIEAuTF9l3FzQRJHUFCvMyTYfxPK1CwaHlXgUmOAtyFQMXmNUAPiQ66bR3TtXhlxztIUOD526Eb0OvDATh7BmLyf2IQL/Uj0SsH11KCledZoVEdLoVUQz5xtvsUDmrp7Ln95RxFVqOxvSfuH/lBjhmYiLoCyYuQFPk5XHFiKghq7a7oAAACBAJZnY/YJqj1F8qay48xfben70GoKfT3rtZ1hXZGY8zbaFn3UQDy2nhHgeVcD2ZeOQoVchsQxl5PqJ1K1pBeWBgrPYpb//20dehOvwxnbB4xkjFc584/1xlmnTr7c5LnNx2VJPcxZACpSvYYPCZQGLNcNQBUNOfq1R1p/X6iv+wfw chfang@pathscale

  reply	other threads:[~2011-04-05 21:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-01 21:53 Fang, Changpeng
2011-04-05 21:49 ` Fang, Changpeng [this message]
2011-04-05 22:15 ` 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=D4C76825A6780047854A11E93CDE84D004DEB2D22E@SAUSEXMBP01.amd.com \
    --to=changpeng.fang@amd.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).