From: Jesper Skov <jskov@redhat.com>
To: overseers@sourceware.cygnus.com
Cc: jskov@redhat.com
Subject: New SSH key
Date: Fri, 16 Jun 2000 02:42:00 -0000 [thread overview]
Message-ID: <200006160942.LAA28711@thinktwice.zoftcorp.dk> (raw)
Message-ID: <20000616024200.q4y9c6p9cTSnRhyKsAJPtNigFesQCjcETxAUBlFgC1c@z> (raw)
Hi
Could I ask you to install this new SSH key for me?
Thanks,
Jesper
1024 37 135115216232492796012403222218578240045656780016789775184778371998685143688696140280621179898537960065880632768220717125998517890948695942512900272203363199274364695114603540630875077253613641955149492082480857718896696589435219888878052044477894854745615925178394794564405467252773768802599293597855713781111 jskov@thinktwice.zoftcorp.dk
next reply other threads:[~2000-06-16 2:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Jesper Skov [this message]
2000-06-16 2:42 ` Jesper Skov
2000-12-30 6:08 ` Jeffrey A Law
2000-06-16 7:16 ` Jeffrey A Law
2004-10-15 16:52 David Gilbert
2004-10-16 1:13 ` Frank Ch. Eigler
2007-06-22 13:56 new ssh key Jonathan Brassow
2008-05-19 22:00 Thiago Jung Bauermann
2008-05-20 0:36 ` Jonathan Larmour
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
2015-12-04 8:50 Richard Henderson
2015-12-04 8:57 ` Ian Lance Taylor
2016-01-12 23:13 new SSH key Ben Elliston
2016-01-13 1:47 ` Ian Lance Taylor
2016-02-04 9:21 New " Simon Dardis
2016-02-04 16:57 ` Ian Lance Taylor
2016-02-04 17:01 ` Simon Dardis
2016-02-05 4:45 ` Ian Lance Taylor
2017-02-22 20:37 new ssh key David Teigland
2017-02-22 20:41 ` Frank Ch. Eigler
2017-05-21 15:00 Thomas Koenig
2017-09-03 12:46 New " Anthony Green
2017-09-03 13:07 ` Frank Ch. Eigler
2020-06-20 17:39 New SSH key Marc Glisse
2020-06-20 20:03 ` Christopher Faylor
2020-06-20 20:36 ` Marc Glisse
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=200006160942.LAA28711@thinktwice.zoftcorp.dk \
--to=jskov@redhat.com \
--cc=overseers@sourceware.cygnus.com \
/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).