From: Jonathan Larmour <jifl@eCosCentric.com>
To: Janus Weil <janus@gcc.gnu.org>
Cc: overseers@gcc.gnu.org
Subject: Re: ssh key
Date: Tue, 24 Jun 2008 11:57:00 -0000 [thread overview]
Message-ID: <48601661.9040502@eCosCentric.com> (raw)
In-Reply-To: <854832d40806210739w1c151df8s73424612d8924f69@mail.gmail.com>
Janus Weil wrote:
> Hello,
>
> I have accidentally nuked my ssh key for accessing gcc.gnu.org. Would
> it be possible to set up a new one (my new key is attached). Sorry for
> the inconvenience.
Done.
Jifl
next prev parent reply other threads:[~2008-06-23 21:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 20:57 Janus Weil
2008-06-24 11:57 ` Jonathan Larmour [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-10-16 22:12 SSH key David Miller
2018-10-16 22:41 ` Ian Lance Taylor
2018-10-16 23:18 ` David Miller
2018-10-16 23:25 ` David Miller
2018-10-16 22:44 ` Frank Ch. Eigler
2004-08-07 16:55 ssh key James A. Morrison
2004-08-09 7:38 ` Christopher Faylor
2004-08-09 14:33 ` Alexandre Oliva
2004-08-09 20:01 ` Christopher Faylor
2004-08-10 17:28 ` Alexandre Oliva
2004-08-10 17:34 ` Frank Ch. Eigler
2004-08-11 14:30 ` Alexandre Oliva
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=48601661.9040502@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=janus@gcc.gnu.org \
--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).