From: the-maldridge <the-maldridge@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: void-release-keys: Add 20230628 signing key.
Date: Tue, 11 Jul 2023 04:13:45 +0200 [thread overview]
Message-ID: <20230711021345.ufIaN0p1sDkBDPBEC_iIS2ifu8aJE0S0M7xRj7Shx50@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44951@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 208 bytes --]
There's a merged pull request on the void-packages repository
void-release-keys: Add 20230628 signing key.
https://github.com/void-linux/void-packages/pull/44951
Description:
Keys staged for image release.
prev parent reply other threads:[~2023-07-11 2:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 3:53 [PR PATCH] " the-maldridge
2023-07-10 4:21 ` [PR PATCH] [Updated] " the-maldridge
2023-07-10 18:25 ` classabbyamp
2023-07-11 2:11 ` the-maldridge
2023-07-11 2:13 ` the-maldridge [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=20230711021345.ufIaN0p1sDkBDPBEC_iIS2ifu8aJE0S0M7xRj7Shx50@z \
--to=the-maldridge@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).