From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>, jmorris@namei.org
Cc: linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [paul@keyserver.paulfurley.com: PGP key expires in 3 days: 0x7179B76704ABA18B (it can be extended)]
Date: Tue, 14 Nov 2017 07:09:34 -0800 [thread overview]
Message-ID: <1510672174.4078.2.camel@HansenPartnership.com> (raw)
In-Reply-To: <20171114062354.j4nrch5xmevllb4l@linux.intel.com>
On Tue, 2017-11-14 at 08:25 +0200, Jarkko Sakkinen wrote:
> James,
>
> Refreshed my key with expiration +2y in keys.gunpg.net and
> pgp.mit.edu.
> Please update.
The way this works in the main tree is that nothing happens until Linus
sees a tag signed with an expired key (which git refuses to pull).
Then he swears a bit, does a pgp refresh and pulls again.
James
prev parent reply other threads:[~2017-11-14 15:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 6:25 [paul@keyserver.paulfurley.com: PGP key expires in 3 days: 0x7179B76704ABA18B (it can be extended)] Jarkko Sakkinen
2017-11-14 15:09 ` James Bottomley [this message]
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=1510672174.4078.2.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.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