From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>, overseers@gcc.gnu.org
Cc: Eric Gallager <egall@gwmail.gwu.edu>
Subject: Re: ssh keys
Date: Mon, 11 Oct 2021 13:48:43 +0200 [thread overview]
Message-ID: <75f74ece3ca9dcdb30030a402720837367df2b2e.camel@klomp.org> (raw)
In-Reply-To: <CAMfHzOu9qUBu8AG7k=vwHZ6QFaoQAhUCyKpEchdCpQG_Z3heYg@mail.gmail.com>
Hi, Eric,
On Sun, 2021-10-10 at 21:46 -0400, Eric Gallager via Overseers wrote:
> Hello GCC Overseers, it's Eric Gallager here, and I'd like to get
> back
> to committing to the GCC project again. The last time I committed was
> back in the SVN days, and it was from a different computer than I
> currently use, and I'm afraid my ssh keys from the old computer got
> lost in the migration process somehow, so if I'm going to get back to
> committing again, I'm going to need to be able to use a new ssh key
> (since I haven't been able to find my old one).
> [...]
> Let me know if there are any other ways I can verify my identity in
> order to get my ssh keys switched, and I apologize for my
> scatterbrainedness in letting this situation arise.
Please sent the ssh pubkey (the ~/.ssh/id_*.pub you are actually using)
and we'll install it for you if you promise to take good care of the
private part.
Cheers,
Mark
next prev parent reply other threads:[~2021-10-11 11:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 1:46 Eric Gallager
2021-10-11 11:48 ` Mark Wielaard [this message]
2021-10-11 19:38 ` Eric Gallager
2021-10-11 19:59 ` Mark Wielaard
-- strict thread matches above, loose matches on Subject: below --
2016-10-13 22:42 Moore, Catherine
2016-10-14 1:04 ` Frank Ch. Eigler
2016-10-14 14:24 ` Moore, Catherine
2006-02-15 4:21 bud davis
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=75f74ece3ca9dcdb30030a402720837367df2b2e.camel@klomp.org \
--to=mark@klomp.org \
--cc=egall@gwmail.gwu.edu \
--cc=overseers@gcc.gnu.org \
--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).