From: Kean Johnston <kean.johnston@gmail.com>
To: overseers@sourceware.org
Subject: Please update SSH key
Date: Tue, 17 Apr 2018 18:14:00 -0000 [thread overview]
Message-ID: <ef38def9-83dd-4770-8d1b-3f2f22b1e9af@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 702 bytes --]
Dear overseers,
I am contacting you on advice from Nick Clifton. I am wanting to start
contributing to binutils / glibc / gcc again, after many years absent from
such work. Back when I worked for SCO I was the official maintainer for GCC
on SCO platforms, a role I want to resume. However, I have long since lost
the SSH key I used when I created my sourceware account so I am unable to
change it myself. Please can you do so for me. My old login was, I believe,
jkj. There is a small chance it was 'kean'. Whichever it was, please can you:
a) Let me know which of those two (jkj or kean) it was and
b) Update the access SSH key to the one attached.
Thank you kindly in advance.
Kean Johnston.
[-- Attachment #2: id_rsa.pub --]
[-- Type: text/plain, Size: 402 bytes --]
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAo3SpWRZ3mlbgmynqD+yt2TvK8q6CuQ+jJt7fjwGK1G734eaYIlANuB5Ste05NK0F7oFfBKaVR5tCJdRTVpfltjYfaZM6lwJu3WmkRnvziK1nsN+pqg3Lt3ufFirmVGOjn+RUp84mkoeHTcdic2pZaK82gIiOVcQpnsAROT7HG5nYl/CgjDlB5H5H0h5MXQqsW/j3fSb0eLvP/eBijXuVu6Fzqlz2MGASV2l1vaUyg9ENdq1hBM/Hu8+0F/MX24QiPpdhi0S+sRbHBdFEKR8VCXX9gmVDHjYDULINLdPTSgnpzkN2HvBObtcsjyY0LoXFLBPt3j+ungj8rU75+81MiQ== ssh@keanjohnston.com
next reply other threads:[~2018-04-17 18:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 18:14 Kean Johnston [this message]
2018-04-24 12:26 ` Ian Lance Taylor
2018-04-26 5:57 ` Kean Johnston
2018-04-26 13:58 ` Frank Ch. Eigler
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=ef38def9-83dd-4770-8d1b-3f2f22b1e9af@gmail.com \
--to=kean.johnston@gmail.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).