From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New package: zam-plugins-3.14
Date: Mon, 06 Jun 2022 04:14:26 +0200 [thread overview]
Message-ID: <20220606021426.VvLn6L2eYiZCxbirleJr4VFnOm4XaJ7TDnZLmGNxeAc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31665@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1588 bytes --]
There's a closed pull request on the void-packages repository
New package: zam-plugins-3.14
https://github.com/void-linux/void-packages/pull/31665
Description:
<!-- Mark items with [x] where applicable -->
Required by `pulseeffects` maximizer effect.
Blocked by https://github.com/void-linux/void-packages/pull/31666.
TODO: fix cross-compilation.
#### General
- [x] 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?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] 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.)
- [ ] 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
-->
prev parent reply other threads:[~2022-06-06 2:14 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-26 16:00 [PR PATCH] " Logarithmus
2021-06-26 19:30 ` [PR REVIEW] " ericonr
2021-06-26 19:30 ` ericonr
2021-06-26 19:30 ` ericonr
2021-06-26 19:30 ` ericonr
2021-06-26 19:30 ` ericonr
2021-06-27 16:00 ` Logarithmus
2021-06-27 16:00 ` Logarithmus
2021-06-27 16:02 ` Logarithmus
2021-06-27 16:36 ` [PR PATCH] [Updated] " Logarithmus
2021-06-27 16:50 ` [PR REVIEW] " Logarithmus
2021-06-27 16:50 ` Logarithmus
2021-06-27 16:50 ` Logarithmus
2021-06-27 16:55 ` Logarithmus
2021-06-27 16:56 ` Logarithmus
2021-06-27 16:57 ` [PR PATCH] [Updated] " Logarithmus
2021-06-27 17:07 ` [PR REVIEW] " Logarithmus
2021-06-27 17:29 ` Logarithmus
2021-06-27 17:30 ` Logarithmus
2021-06-27 17:51 ` ericonr
2021-06-27 17:51 ` ericonr
2021-06-27 17:53 ` Logarithmus
2021-06-27 18:01 ` ericonr
2021-06-27 18:33 ` Logarithmus
2021-06-27 18:45 ` ericonr
2021-06-27 19:02 ` Duncaen
2021-06-27 19:04 ` Logarithmus
2021-06-27 19:23 ` [PR PATCH] [Updated] " Logarithmus
2021-06-27 19:56 ` Logarithmus
2021-06-27 20:35 ` [PR PATCH] [Updated] " Logarithmus
2021-06-27 21:15 ` Logarithmus
2021-06-27 21:32 ` Logarithmus
2021-06-27 21:37 ` Logarithmus
2021-06-27 21:50 ` Logarithmus
2021-06-27 21:59 ` Logarithmus
2021-06-28 0:21 ` Logarithmus
2022-05-23 2:12 ` github-actions
2022-06-06 2:14 ` github-actions [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=20220606021426.VvLn6L2eYiZCxbirleJr4VFnOm4XaJ7TDnZLmGNxeAc@z \
--to=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).