From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: New package: openpgp-ca-0.11.2
Date: Wed, 01 Feb 2023 12:46:38 +0100 [thread overview]
Message-ID: <20230201114638.8Pl-Q1MSwWtUWvZ5TUYLBALyLFWY4btIkuJ5BJ55FP4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37588@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
There's a merged pull request on the void-packages repository
New package: openpgp-ca-0.11.2
https://github.com/void-linux/void-packages/pull/37588
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
I've created a CA, created some users and checked the generated certificates using `sq`. The output looks good.
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64 - crossbuild
prev parent reply other threads:[~2023-02-01 11:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 20:05 [PR PATCH] New package: openpgp-ca-0.10.1 jcgruenhage
2022-08-01 14:08 ` [PR PATCH] [Updated] " jcgruenhage
2022-10-31 2:15 ` New package: openpgp-ca-0.11.1 github-actions
2022-11-01 13:46 ` [PR PATCH] [Updated] " jcgruenhage
2022-11-01 13:46 ` jcgruenhage
2023-02-01 2:07 ` New package: openpgp-ca-0.11.2 github-actions
2023-02-01 10:11 ` jcgruenhage
2023-02-01 10:43 ` [PR PATCH] [Updated] " sgn
2023-02-01 10:43 ` sgn
2023-02-01 10:58 ` sgn
2023-02-01 11:01 ` sgn
2023-02-01 11:46 ` sgn [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=20230201114638.8Pl-Q1MSwWtUWvZ5TUYLBALyLFWY4btIkuJ5BJ55FP4@z \
--to=sgn@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).