From: Jonathan Corbet <corbet@lwn.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-doc@vger.kernel.org
Subject: Re: [GIT PULL] Documentation for 5.0
Date: Mon, 31 Dec 2018 15:13:27 -0700 [thread overview]
Message-ID: <20181231151327.404ee4d8@lwn.net> (raw)
In-Reply-To: <CAHk-=wj8=xoaS=QJXRMo70Si0E5xvJmdyA2-cu99_MA_FjhHTA@mail.gmail.com>
On Sat, 29 Dec 2018 11:24:34 -0800
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> New signing key? And one that you forgot to push out to keyservers?
Sort of...some time ago, I tried to be a good kid and made a separate
signing subkey like Konstantin told me to. Then I couldn't ever get the
nitrokey thing to work and then got distracted; I guess I never uploaded
that key. I'm not really sure why gpg decided to start using it now.
It's uploaded now, anyway.
TLDR: I kind of suck at this gpg thing. Sorry for the confusion.
jon
next prev parent reply other threads:[~2018-12-31 22:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-28 16:06 [GIT PULL] Documentation for 5.0 Jonathan Corbet
2018-12-29 19:24 ` Linus Torvalds
2018-12-31 22:13 ` Jonathan Corbet [this message]
2018-12-29 19:55 ` 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=20181231151327.404ee4d8@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@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).