From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: pass-import: update to version 3.2
Date: Sat, 13 Nov 2021 22:59:54 +0100 [thread overview]
Message-ID: <20211113215954.UYaBqdMz6X5VfRNNz1ZnV5lYQAbIVhKGssP68owfFrA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32091@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1447 bytes --]
There's a merged pull request on the void-packages repository
pass-import: update to version 3.2
https://github.com/void-linux/void-packages/pull/32091
Description:
<!-- Mark items with [x] where applicable -->
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ x] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [x ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
next prev parent reply other threads:[~2021-11-13 21:59 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 12:44 [PR PATCH] " adbrown101
2021-07-21 19:22 ` ericonr
2021-07-22 21:11 ` [PR PATCH] [Updated] " adbrown101
2021-07-22 21:16 ` adbrown101
2021-07-23 1:43 ` [PR REVIEW] " sgn
2021-07-24 8:02 ` adbrown101
2021-07-24 10:14 ` paper42
2021-07-25 10:21 ` [PR PATCH] [Updated] " adbrown101
2021-07-25 15:34 ` adbrown101
2021-07-25 15:37 ` [PR REVIEW] " adbrown101
2021-07-25 16:29 ` paper42
2021-07-25 16:30 ` [PR REVIEW] " paper42
2021-07-26 16:56 ` [PR PATCH] [Updated] " adbrown101
2021-07-26 16:59 ` adbrown101
2021-07-26 17:03 ` [PR REVIEW] " adbrown101
2021-07-26 17:07 ` adbrown101
2021-07-26 18:13 ` paper42
2021-07-26 18:15 ` [PR REVIEW] " paper42
2021-07-26 18:18 ` paper42
2021-07-26 18:18 ` paper42
2021-07-27 12:34 ` [PR REVIEW] " adbrown101
2021-07-27 12:36 ` adbrown101
2021-07-27 12:37 ` adbrown101
2021-07-27 12:41 ` paper42
2021-07-27 17:00 ` [PR PATCH] [Updated] " adbrown101
2021-07-27 17:05 ` adbrown101
2021-07-27 18:02 ` paper42
2021-07-28 16:53 ` adbrown101
2021-07-28 20:12 ` paper42
2021-11-10 0:19 ` paper42
2021-11-11 12:03 ` adbrown101
2021-11-12 17:35 ` [PR PATCH] [Updated] " adbrown101
2021-11-12 18:08 ` [PR REVIEW] " paper42
2021-11-12 18:16 ` paper42
2021-11-12 18:16 ` paper42
2021-11-13 12:16 ` [PR PATCH] [Updated] " adbrown101
2021-11-13 12:17 ` adbrown101
2021-11-13 15:07 ` [PR PATCH] [Updated] " adbrown101
2021-11-13 21:59 ` paper42 [this message]
2021-11-16 13:09 ` adbrown101
2021-11-16 13:40 ` paper42
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=20211113215954.UYaBqdMz6X5VfRNNz1ZnV5lYQAbIVhKGssP68owfFrA@z \
--to=paper42@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).