From: Ralf Mardorf <ralf.mardorf@alice-dsl.net>
To: linux-rt-users <linux-rt-users@vger.kernel.org>,
Daniel Wagner <wagi@monom.org>
Subject: Re: [ANNOUNCE] 4.19.233-rt105
Date: Fri, 18 Mar 2022 10:27:18 +0100 [thread overview]
Message-ID: <20220318102718.1347247d@archlinux> (raw)
In-Reply-To: <20220318102051.483333f2@archlinux>
On Fri, 18 Mar 2022 10:20:51 +0100, Ralf Mardorf wrote:
>On Fri, 18 Mar 2022 09:48:00 +0100, Daniel Wagner wrote:
>>On Fri, Mar 18, 2022 at 06:01:51AM +0100, Ralf Mardorf wrote:
>>> On Fri, 11 Mar 2022 09:19:04 +0100, Daniel Wagner wrote:
>>> >Signing key fingerprint:
>>> >
>>> > 5BF6 7BC5 0826 72CA BB45 ACAE 587C 5ECA 5D0A 306C
>>>
>>> Hi,
>>>
>>> where is actually the required key (E072D068B1F5703E) uploaded, to
>>> verify the patch?
>>
>>Sorry, forgot to add this to the announce template. The key is
>>available on the korg keyring:
>>
>> git://git.kernel.org/pub/scm/docs/kernel/pgpkeys.git
>>
>>FWIW, I have a TODO for this:
>>
>> https://github.com/igaw/stable-rt-tools/issues/11
>
>Hi,
>
>I can't find the key
>
>1B45744BE36280CA7D6BD460E072D068B1F5703E
>short E072D068B1F5703E
>
>at
>https://kernel.googlesource.com/pub/scm/docs/kernel/pgpkeys/+/refs/heads/master
>
>*?*
>Ralf
Actually I don't want to upload something, I want to download the
needed key to verify the rt-patch. It's not available by any public
key server I used when trying to get the public key.
next prev parent reply other threads:[~2022-03-18 9:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 8:19 [ANNOUNCE] 4.19.233-rt105 Daniel Wagner
2022-03-18 5:01 ` Ralf Mardorf
2022-03-18 8:48 ` Daniel Wagner
[not found] ` <20220318102051.483333f2@archlinux>
2022-03-18 9:27 ` Ralf Mardorf [this message]
2022-03-18 9:45 ` Daniel Wagner
2022-03-18 17:00 ` Ralf Mardorf
2022-03-18 17:42 ` Ralf Mardorf
2022-03-21 8:36 ` Daniel Wagner
2022-03-21 10:13 ` Ralf Mardorf
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=20220318102718.1347247d@archlinux \
--to=ralf.mardorf@alice-dsl.net \
--cc=linux-rt-users@vger.kernel.org \
--cc=wagi@monom.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.