From: Ian Lance Taylor <ian@airs.com>
To: Simon Dardis <Simon.Dardis@imgtec.com>
Cc: "overseers@gcc.gnu.org" <overseers@gcc.gnu.org>
Subject: Re: New SSH key.
Date: Thu, 04 Feb 2016 16:57:00 -0000 [thread overview]
Message-ID: <m3egcsxvk5.fsf@pepe.airs.com> (raw)
In-Reply-To: <B83211783F7A334B926F0C0CA42E32CA0110A98C@hhmail02.hh.imgtec.org> (Simon Dardis's message of "Thu, 4 Feb 2016 09:21:01 +0000")
Simon Dardis <Simon.Dardis@imgtec.com> writes:
> Could my current SSH key be replaced with the attached one?
You should be able to do it yourself using
ssh dardiss@gcc.gnu.org replacekey < NEWKEY
Let us know if that doesn't work.
Ian
next prev parent reply other threads:[~2016-02-04 16:57 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 9:21 Simon Dardis
2016-02-04 16:57 ` Ian Lance Taylor [this message]
2016-02-04 17:01 ` Simon Dardis
2016-02-05 4:45 ` Ian Lance Taylor
-- strict thread matches above, loose matches on Subject: below --
2020-06-20 17:39 Marc Glisse
2020-06-20 20:03 ` Christopher Faylor
2020-06-20 20:36 ` Marc Glisse
2017-09-03 12:46 New ssh key Anthony Green
2017-09-03 13:07 ` Frank Ch. Eigler
2017-05-21 15:00 new " Thomas Koenig
2017-02-22 20:37 David Teigland
2017-02-22 20:41 ` Frank Ch. Eigler
2016-01-12 23:13 new SSH key Ben Elliston
2016-01-13 1:47 ` Ian Lance Taylor
2015-12-04 8:50 new ssh key Richard Henderson
2015-12-04 8:57 ` Ian Lance Taylor
2008-06-02 19:20 Ralf Wildenhues
2008-06-02 19:41 ` Christopher Faylor
2008-06-02 20:00 ` Ralf Wildenhues
2008-06-05 3:56 ` Christopher Faylor
2008-06-06 15:22 ` Ralf Wildenhues
2008-05-19 22:00 Thiago Jung Bauermann
2008-05-20 0:36 ` Jonathan Larmour
2007-06-22 13:56 Jonathan Brassow
2004-10-15 16:52 New SSH key David Gilbert
2004-10-16 1:13 ` Frank Ch. Eigler
2000-12-30 6:08 Jesper Skov
2000-06-16 2:42 ` Jesper Skov
2000-12-30 6:08 ` Jeffrey A Law
2000-06-16 7:16 ` Jeffrey A Law
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=m3egcsxvk5.fsf@pepe.airs.com \
--to=ian@airs.com \
--cc=Simon.Dardis@imgtec.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).