Return-Path: Received: from mail-it0-f68.google.com ([209.85.214.68]:33772 "EHLO mail-it0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753881AbdGNLdU (ORCPT ); Fri, 14 Jul 2017 07:33:20 -0400 Subject: Re: [GIT PULL] Please pull NFS client changes for Linux 4.13 To: Christoph Hellwig , Linus Torvalds Cc: Linux NFS Mailing List , linux-fsdevel , Linux Kernel Mailing List , "J. Bruce Fields" References: <20170714070922.GA10669@infradead.org> From: Anna Schumaker Message-ID: Date: Fri, 14 Jul 2017 07:33:16 -0400 MIME-Version: 1.0 In-Reply-To: <20170714070922.GA10669@infradead.org> Content-Type: text/plain; charset=utf-8 Sender: linux-nfs-owner@vger.kernel.org List-ID: On 07/14/2017 03:09 AM, Christoph Hellwig wrote: > On Thu, Jul 13, 2017 at 02:43:14PM -0700, Linus Torvalds wrote: >> On Thu, Jul 13, 2017 at 2:16 PM, Anna Schumaker >> wrote: >>> >>> git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-4.13-1 >> >> Btw, your key seems to have expired, and doing a refresh on it doesn't fix it. >> >> I'm sure you've refreshed your key, but apparently that refresh hasn't >> been percolated to the public keyservers? I assumed I had refreshed it once git let me sign things again, but maybe I missed a step. > > As someone who has run into an issue in that area recently: I manually > had to refresh and re-upload my signing subkey and not just the primary > key, which wa rather confusing and took a long time to sort out. > I'll start here. Thanks for the tip! Anna