From: "Uwe Kleine-König" <ukleinek@kernel.org>
To: users@linux.kernel.org
Cc: linux-kernel@vger.kernel.org,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
lpcosse-keysigning@baylibre.com
Subject: PGP keysigning at LPC/OSSE 2026 (Reminder for registration)
Date: Tue, 15 Sep 2026 10:16:10 +0200 [thread overview]
Message-ID: <aqj-ylAvjuHZeOan@monoceros> (raw)
[-- Attachment #1: Type: text/plain, Size: 1765 bytes --]
Hello,
this is a reminder for the PGP keysigning event held during Linux
Plumbers and Open Source Summit Europe in Prague this October.
While it's not mandatory, it will speed up and simplify the processes if
you register with your certificate for the event. Please do so by
sending your public key to lpcosse-keysigning@baylibre.com until
2026-09-27 08:00 UTC. If you saw the initial announcement[1] and thought
it was still to early and I'm on vacation, please hit reply now and
attach (or include inline) your certificate which can probably be
generated using:
gpg --export --armor your-email-address@example.com
.
I will create a list of all registrants and their certificates such that
you will end up with less small paper strips to handle. It will also
help me to estimate the size of the group such that an appropriate place
for the meeting can be selected.
Note the list of participants will be public. It contains essentially
the info from your certificate. If you have concerns about that, please
don't register. (But note that if you're using your key in the
community, the same information is out there anyhow.)
As long as my time permits, I will also look at the certificates I
receive and point out things that might be worth doing before the event.
So in your own interest don't wait until a few seconds before the
registration deadline. Also if I don't reply that's a strong hint that
Google didn't accept your mail. Sending your mail early allows to catch
that.
If things are unclear, don't hesitate to ask. I created
#lpcosse2026-keysigning on the libera irc network for that, or send me
an email to the above email alias.
Looking forward to meet you in Prague,
Uwe
[1] https://lore.kernel.org/lkml/lpcosse2026-keysigning@baylibre.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-09-15 8:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 8:16 Uwe Kleine-König [this message]
2026-09-20 8:35 ` Geert Uytterhoeven
2026-09-20 10:10 ` 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=aqj-ylAvjuHZeOan@monoceros \
--to=ukleinek@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpcosse-keysigning@baylibre.com \
--cc=users@linux.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
all inboxes | Powered by JetHome®