keys.linux.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Stephen Brennan <stephen.s.brennan@oracle.com>
Cc: keys@linux.kernel.org
Subject: Re: Keys for Stephen Brennan
Date: Mon, 22 Aug 2022 13:16:34 -0400	[thread overview]
Message-ID: <20220822171634.ynfqwr2rj3762inx@meerkat.local> (raw)
In-Reply-To: <877d30kyij.fsf@oracle.com>

On Mon, Aug 22, 2022 at 09:56:36AM -0700, Stephen Brennan wrote:
> I guess I missed all the changes to keyservers not distributing third
> party signatures anymore! I just assumed that a "--recv-key" would get
> my signatures but I need to manually copy the exported key these days.
> 
> I've attached re-exported key with third-party signatures.

Okay, I've added your key with a single path through Luis Chamberlain.

-K

      reply	other threads:[~2022-08-22 17:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-20  0:10 Keys for Stephen Brennan Stephen Brennan
2022-08-22 15:00 ` Konstantin Ryabitsev
2022-08-22 16:56   ` Stephen Brennan
2022-08-22 17:16     ` Konstantin Ryabitsev [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=20220822171634.ynfqwr2rj3762inx@meerkat.local \
    --to=konstantin@linuxfoundation.org \
    --cc=keys@linux.kernel.org \
    --cc=stephen.s.brennan@oracle.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 NNTP newsgroup(s).