public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Eric Gallager <egall@gwmail.gwu.edu>
To: overseers@gcc.gnu.org
Subject: ssh keys
Date: Sun, 10 Oct 2021 21:46:11 -0400	[thread overview]
Message-ID: <CAMfHzOu9qUBu8AG7k=vwHZ6QFaoQAhUCyKpEchdCpQG_Z3heYg@mail.gmail.com> (raw)

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). My "@gcc.gnu.org"
email address is egallager@gcc.gnu.org (it forwards to this address
egall@gwmail.gwu.edu that I'm currently writing from), and I have
mentioned this issue with my keys with that account on Bugzilla, for
example, here: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56604
My original sponsor when I first applied for commit access was David
Malcolm, and I still have a copyright assignment on file with the FSF
(which I visited in person to deliver), so you can contact them if
necessary. Also I was asking about this issue on the #gcc IRC channel
on oftc.net, where Iain Sandoe recommended I email the overseers about
it, so he can vouch for me, too.
This is also something I've mentioned on my Twitter account:
https://twitter.com/cooljeanius/status/1413700314398666753?s=21
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.
Thanks,
Eric Gallager

             reply	other threads:[~2021-10-11  1:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-11  1:46 Eric Gallager [this message]
2021-10-11 11:48 ` Mark Wielaard
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='CAMfHzOu9qUBu8AG7k=vwHZ6QFaoQAhUCyKpEchdCpQG_Z3heYg@mail.gmail.com' \
    --to=egall@gwmail.gwu.edu \
    --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).