Re: Commits in keyring without trackable emails

[Konstantin Ryabitsev]

On Fri, Oct 23, 2026 at 09:21:05AM +0200, Krzysztof Kozlowski wrote:
> A few recent commits like bbecf3f1a77b ("Add AE1C2FBEA7DB42E1 (Troy
> Mitchell)") have message Id which points nowhere.
> 
> Last three commits:
> 
> https://lore.kernel.org/r/7ia41p9k58ci.fsf@xxxxxxxxxxxxxxxxxxxxx/
> https://lore.kernel.org/r/010001a153609a07-82ca770b-3c4e-41e2-922a-92aa9475eee8-000000@xxxxxxxxxxxxxxxxxxx
> 
> https://lore.kernel.org/r/20261015152222.000053c6@xxxxxxxxx/
> 
> How were these updates received? Why aren't they on keys@ mailing list?

It was never a requirement that all key updates must be sent via the keys@
mailing list. Some of them are sent as part of kernel.org account request to
the non-public helpdesk address. They are tracked using the Message-Id as
opposed to a Link trailer.

Many key updates land on the keyring list via routine keyserver updates --
they carry no provenance indicators at all.

-K