From: Jonathan Larmour <jifl@eCosCentric.com>
To: Ollie Wild <aaw@google.com>
Cc: overseers@gcc.gnu.org
Subject: Re: public key request for aaw@gcc.gnu.org
Date: Wed, 28 May 2008 14:02:00 -0000 [thread overview]
Message-ID: <483C6030.9030707@eCosCentric.com> (raw)
In-Reply-To: <65dd6fd50805271145y32c41c7ey96760912be4423de@mail.gmail.com>
Ollie Wild wrote:
> Hi,
>
> The home machine I normally use to submit changes to gcc is having
> hard drive problems. Until I get these sorted out, I'd like to start
> using my work desktop.
>
> Would it be possible to get the attached public key added to my list
> of valid ssh keys?
I assume you don't have access to your home machine data now so can't use
the following:
ssh sourceware.org appendkey < id_dsa.pub
so I have added the key for you.
Jifl
--
eCosCentric Limited http://www.eCosCentric.com/ The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["Si fractum non sit, noli id reficere"]------ Opinions==mine
prev parent reply other threads:[~2008-05-27 19:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-28 7:02 Ollie Wild
2008-05-28 14:02 ` Jonathan Larmour [this message]
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=483C6030.9030707@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=aaw@google.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).