From: Andrea Corallo <Andrea.Corallo@arm.com>
To: Ian Lance Taylor <ian@airs.com>
Cc: "overseers@gcc.gnu.org" <overseers@gcc.gnu.org>, nd <nd@arm.com>
Subject: Re: Gcc repo write access
Date: Tue, 14 Jan 2020 14:09:00 -0000 [thread overview]
Message-ID: <gkr4kwyp1sx.fsf@arm.com> (raw)
In-Reply-To: <m3wo9utaym.fsf@pepe.airs.com> (Ian Lance Taylor's message of "Tue, 14 Jan 2020 05:38:09 -0800")
[-- Attachment #1: Type: text/plain, Size: 674 bytes --]
Ian Lance Taylor <ian@airs.com> writes:
> Andrea Corallo <Andrea.Corallo@arm.com> writes:
>
>> I'd like to install a new public ssh key on sourceware.org for gcc write
>> access. Unfortunately due to reinstall I've lost my old keys so I
>> can't do it myself (my apologies).
>>
>> What is the procedure to have the new public key installed?
>
> If you've lost your private key, then the procedure is to send your new
> public key to this mailing list, along with your login name.
>
> Please don't lose your private key again, though. Thanks.
>
> Ian
Hi Ian,
My login name is akrl, attached is my new public key.
Thanks in advance
Andrea
[-- Attachment #2: id_rsa_gcc.pub --]
[-- Type: application/octet-stream, Size: 412 bytes --]
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC5DYS75Y54ccozznhF2G/VwwUJ5SMpYxvzq1JKD7i1e6AyKSM+Bj4pGY3ic5LquFiagLH+ujCgmnbKj4nb4L/V8T1N8eCmreNpnN0OR9apNDS8peinsp6jF+uSoH8VBIeqBLW/jWYyFjeUsISdz2ZVoYPtCafb7hCe2qEIl6DrNBh18OOL2wYuWcKEQfg2i/fmEsf1KvVTaW0Z8B1ED6pUz3fFWvz8namjaKD8kMP7ZJLXulQi3AtQJ+dQGJ/PvF3tLZgeupiRDGnhj5sz/Qo+Hn9pc4UQltOk+9l8YZtgYmeUPnA/VPFcp/Do4Z9DVk+MjUX0ykM40FqGtpGQRHdX andrea.corallo@arm.com for GCC
next prev parent reply other threads:[~2020-01-14 14:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 9:53 Andrea Corallo
2020-01-14 13:38 ` Ian Lance Taylor
2020-01-14 14:09 ` Andrea Corallo [this message]
2020-01-16 10:14 ` Andrea Corallo
2020-02-06 8:57 ` Andrea Corallo
2020-02-06 14:53 ` Frank Ch. Eigler
2020-02-06 15:06 ` Andrea Corallo
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=gkr4kwyp1sx.fsf@arm.com \
--to=andrea.corallo@arm.com \
--cc=ian@airs.com \
--cc=nd@arm.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).