From: David Gibson <david@gibson.dropbear.id.au>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: keys@linux.kernel.org
Subject: Re: New key
Date: Fri, 10 Feb 2023 11:06:44 +1100 [thread overview]
Message-ID: <Y+WKlLtsY4RkqEnV@yekko> (raw)
In-Reply-To: <20230209204114.ynajycsawbmjugxj@meerkat.local>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
On Thu, Feb 09, 2023 at 03:41:14PM -0500, Konstantin Ryabitsev wrote:
> On Thu, Feb 09, 2023 at 09:53:30PM +1100, David Gibson wrote:
> > Accidentally revoked the old one :(
>
> Sorry to hear that, but as there are no signatures on your new key that we
> recognize, we cannot add it to the keyring. Would you be able to get more
> people to sign your key?
I'm working on it, got my order of operations a bit mixed up. It is
signed by my old key... but alas only after it was revoked, so that
probably doesn't count. I should be able to get a signature from
Stephen Rothwell in the nearish future.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-02-10 0:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 10:53 New key David Gibson
2023-02-09 20:41 ` Konstantin Ryabitsev
2023-02-10 0:06 ` David Gibson [this message]
[not found] ` <Y+mh9AALS6uCC/0A@yekko>
2023-02-21 22:28 ` Konstantin Ryabitsev
2023-02-22 3:42 ` David Gibson
2023-02-23 16:19 ` Konstantin Ryabitsev
2023-02-24 4:05 ` David Gibson
2023-02-24 4:21 ` David Gibson
-- strict thread matches above, loose matches on Subject: below --
2023-04-14 15:30 Konrad Dybcio
2023-04-17 16:35 ` Konstantin Ryabitsev
2023-05-09 9:51 Konrad Dybcio
2023-05-09 18:49 ` Konstantin Ryabitsev
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=Y+WKlLtsY4RkqEnV@yekko \
--to=david@gibson.dropbear.id.au \
--cc=keys@linux.kernel.org \
--cc=konstantin@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.