Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Message-ID: <dd3a1ec7d03888dade78db1e4c45ec1347c0815b.camel@tiscali.nl>
Subject: Re: Linux 5.2.10
From:   Paul Bolle <pebolle@tiscali.nl>
To:     Sasha Levin <sashal@kernel.org>, linux-kernel@vger.kernel.org,
        stable@vger.kernel.org, akpm@linux-foundation.org
Cc:     jslaby@suse.cz, lwn@lwn.net
Date:   Sun, 25 Aug 2019 19:33:36 +0200
In-Reply-To: <20190825144703.6518-1-sashal@kernel.org>
References: <20190825144703.6518-1-sashal@kernel.org>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.32.4 (3.32.4-1.fc30) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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@kernel.org but signed by 
alexander.levin@verizon.com. Perhaps you could use one of gpg2's many options
to add an
    aka "Sasha Levin <sashal@kernel.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