[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dd3a1ec7d03888dade78db1e4c45ec1347c0815b.camel@tiscali.nl>
Date: Sun, 25 Aug 2019 19:33:36 +0200
From: Paul Bolle <pebolle@...cali.nl>
To: Sasha Levin <sashal@...nel.org>, linux-kernel@...r.kernel.org,
stable@...r.kernel.org, akpm@...ux-foundation.org
Cc: jslaby@...e.cz, lwn@....net
Subject: Re: Linux 5.2.10
Sasha,
Sasha Levin schreef op zo 25-08-2019 om 10:47 [-0400]:
> I'm announcing the release of the 5.2.10 kernel.
>
> All users of the 5.2 kernel series must upgrade.
>
> The updated 5.2.y git tree can be found at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.2.y
> and can be browsed at the normal kernel.org git web browser:
> https://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
v5.2.10 was tagged by sashal@...nel.org but signed by
alexander.levin@...izon.com. Perhaps you could use one of gpg2's many options
to add an
aka "Sasha Levin <sashal@...nel.org>"
line to that key. (I assume "--recv-key" then would have found your key.)
Or would that be a sin against kernel.org policy, state-of-the-art
cryptographic practices, or whatever?
Thanks,
Paul Bolle
Powered by blists - more mailing lists