public inbox for keys@kernel.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: Konstantin Ryabitsev <mricon@kernel.org>
Cc: keys@linux.kernel.org, Yanteng Si <siyanteng01@gmail.com>,
	 Zhi Wang <zhi.wang.linux@gmail.com>,
	Zhi Wang <zhi.a.wang@intel.com>, Jessica Yu <jeyu@kernel.org>,
	 Jessica Yu <jeyu@posteo.de>, Jessica Yu <jeyu@suse.de>,
	 Neeraj Upadhyay <neeraj.iitr10@gmail.com>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	 Daniel Lezcano <daniel.lezcano@free.fr>,
	Daniel Lezcano <daniel.lezcano@linexp.org>,
	 Frank Rowand <key_111017@frowand.com>,
	Frank Rowand <frowand@gmail.com>,
	 Frank Rowand <frowand.list@gmail.com>,
	Frank Rowand <frank@frowand.com>
Subject: Re: [PATCH] Remove keys that expired in 2025
Date: Sat, 14 Feb 2026 00:15:27 +0100	[thread overview]
Message-ID: <aY-sHT72c3jHO-ZN@monoceros> (raw)
In-Reply-To: <20260213-enlightened-white-mantis-3ebfd6@lemur>

[-- Attachment #1: Type: text/plain, Size: 1418 bytes --]

Hello Konstantin,

[dropped a few addresses from Cc: that bounced before]

On Fri, Feb 13, 2026 at 04:51:16PM -0500, Konstantin Ryabitsev wrote:
> On Thu, Jan 22, 2026 at 10:20:20AM +0100, Uwe Kleine-König wrote:
> > there are three keys with UIDs that I think Konstantin invented. i.e.:
> > 
> > Bothersome Borer <bothersome-borer@kernel.org>
> > Confounding Cockroach <confounding-cockroach@kernel.org>
> > Aggravating Aphid <aggravating-aphid@kernel.org>
> > 
> > Not sure what they are used for, but I guess Konstantin knows if they
> > can/should go away.
> 
> I'm slowly going through my backlog -- thank you for your patience. This
> patch no longer applies, I think because some keys actually got updated since
> then.

Yeah, just skip the changes to the key files that don't apply any more
(together with the respective changes to graphs/ and .keyring).

You can check your result against
8e5424c89f5602904e308e89cc8bd49fe3f92600 that is contained in

	https://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/pgpkeys.git master

Tell me if a resend of the updated change helps you.

> To explain what the above ones are for, they are used by remail:
> https://korg.docs.kernel.org/remail.html
> 
> The keys are created as needed with a 5-year expiry, so they can indeed be
> removed now.

OK, then the patch should be fine and doesn't need an update.

Best regards
Uwe

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2026-02-13 23:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-22  9:20 [PATCH] Remove keys that expired in 2025 Uwe Kleine-König
2026-02-13 21:51 ` Konstantin Ryabitsev
2026-02-13 23:15   ` Uwe Kleine-König [this message]
2026-03-19 17:51     ` Uwe Kleine-König

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=aY-sHT72c3jHO-ZN@monoceros \
    --to=u.kleine-koenig@baylibre.com \
    --cc=daniel.lezcano@free.fr \
    --cc=daniel.lezcano@linaro.org \
    --cc=daniel.lezcano@linexp.org \
    --cc=frank@frowand.com \
    --cc=frowand.list@gmail.com \
    --cc=frowand@gmail.com \
    --cc=jeyu@kernel.org \
    --cc=jeyu@posteo.de \
    --cc=jeyu@suse.de \
    --cc=key_111017@frowand.com \
    --cc=keys@linux.kernel.org \
    --cc=mricon@kernel.org \
    --cc=neeraj.iitr10@gmail.com \
    --cc=siyanteng01@gmail.com \
    --cc=zhi.a.wang@intel.com \
    --cc=zhi.wang.linux@gmail.com \
    /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