From: Wei Liu <wei.liu@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Wei Liu <wei.liu@kernel.org>,
Linux Kernel List <linux-kernel@vger.kernel.org>,
Linux on Hyper-V List <linux-hyperv@vger.kernel.org>,
kys@microsoft.com, haiyangz@microsoft.com, decui@microsoft.com
Subject: Re: [GIT PULL] Hyper-V commits for 6.9
Date: Sat, 23 Mar 2024 00:06:17 +0000 [thread overview]
Message-ID: <Zf4c-WYt2uhYXiPm@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <CAHk-=wgfVQyT49aTbgY3_Z4iVxEwvxkj12YiW+WD_HrM_8V3cQ@mail.gmail.com>
On Fri, Mar 22, 2024 at 04:42:50PM -0700, Linus Torvalds wrote:
> On Fri, 22 Mar 2024 at 16:25, Wei Liu <wei.liu@kernel.org> wrote:
> >
> > Hmm... I thought I refreshed it right before the expiration date. I
> > pushed it to Ubuntu's keyserver.
>
> Ok, I can find it there.
>
> > I will check if something's wrong.
> >
> > Do you have a keyserver that you prefer?
>
> The problem with keyservers is that there's so many of them, and
> everybody uses different keyservers, and the propagation of pgp keys
> across keyservers hasn't really worked for over a decade by now.
I noticed that keys do eventually propagate, but I never had the means
to time how long it takes.
>
> Maybe keys eventually propagate, but I have my doubts.
>
> My default keyserver appears to be hkps://keys.openpgp.org, but the
> pgp key git tree on kernel.org is the one I then look at when some key
> isn't there (or is there, but hasn't been updated).
>
Okay, so my key in that git repository has not been updated. And the
last time it was updated was in Jan 2023 (!). I thought it was updated
more often by a cron job but apparently not.
I will drop an email to keys@linux.kernelorg to refresh the key.
Thanks,
Wei.
> Linus
next prev parent reply other threads:[~2024-03-23 0:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 4:09 [GIT PULL] Hyper-V commits for 6.9 Wei Liu
2024-03-21 17:06 ` Linus Torvalds
2024-03-22 23:25 ` Wei Liu
2024-03-22 23:42 ` Linus Torvalds
2024-03-23 0:06 ` Wei Liu [this message]
2024-03-21 17:34 ` pr-tracker-bot
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=Zf4c-WYt2uhYXiPm@liuwe-devbox-debian-v2 \
--to=wei.liu@kernel.org \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).