From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Roger Sayle <roger@nextmovesoftware.com>, sayle@gnu.org
Subject: Re: Updating public key for sayle@gcc.gnu.org
Date: Sat, 27 Jun 2020 23:07:33 +0200 [thread overview]
Message-ID: <20200627210733.GC6605@wildebeest.org> (raw)
In-Reply-To: <005301d64cbd$8afa7cd0$a0ef7670$@nextmovesoftware.com>
Hi Rogers,
On Sat, Jun 27, 2020 at 09:00:00PM +0100, Roger Sayle via Overseers wrote:
> I've now generated a new 4096-bit RSA key pair, and was wondering
> whether you could please update my access permissions/credentials on
> gcc.gnu.org with the attached sayle.pub? To help prove that this
> really is me, I've also uploaded the exact same file as
> ~sayle/sayle.pub on fencepost.gnu.org, which should at least prove
> that I have the old private key.
Welcome back Jedi. New code accepted and installed.
Cheers,
Mark
prev parent reply other threads:[~2020-06-27 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-27 20:00 Roger Sayle
2020-06-27 21:07 ` Mark Wielaard [this message]
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=20200627210733.GC6605@wildebeest.org \
--to=mark@klomp.org \
--cc=overseers@sourceware.org \
--cc=roger@nextmovesoftware.com \
--cc=sayle@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).