From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: New package: hydrus-525a
Date: Wed, 28 Jun 2023 22:07:35 +0200 [thread overview]
Message-ID: <20230628200735.HamWln0F18TrJxOXRlJ5NbC4F2Q8Nsw7TB9lr9Jd-BQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35034@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
There's a merged pull request on the void-packages repository
New package: hydrus-525a
https://github.com/void-linux/void-packages/pull/35034
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
#### Local build testing
- I built this PR locally for my native architecture, (x86_64)
prev parent reply other threads:[~2023-06-28 20:07 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 18:27 [PR PATCH] New package: hydrus-468 fanyx
2022-01-13 19:49 ` [PR PATCH] [Updated] " fanyx
2022-02-20 13:33 ` [PR PATCH] [Updated] New package: hydrus-469 fanyx
2022-06-08 9:50 ` [PR PATCH] [Updated] New package: hydrus-474 fanyx
2022-06-08 9:51 ` fanyx
2022-06-10 15:21 ` fanyx
2022-06-10 15:37 ` fanyx
2022-06-10 15:40 ` [PR PATCH] [Updated] New package: hydrus-488d fanyx
2022-09-09 2:15 ` github-actions
2022-09-09 9:48 ` [PR PATCH] [Updated] " fanyx
2022-09-20 13:51 ` New package: hydrus-499 fanyx
2022-09-20 13:54 ` [PR PATCH] [Updated] " fanyx
2022-09-20 14:11 ` fanyx
2022-09-20 14:16 ` fanyx
2022-09-20 14:36 ` fanyx
2022-10-05 19:20 ` RunningDroid
2022-10-05 19:23 ` [PR REVIEW] " RunningDroid
2022-10-11 10:36 ` [PR PATCH] [Updated] " fanyx
2022-10-11 10:36 ` [PR REVIEW] " fanyx
2022-10-11 10:36 ` fanyx
2022-10-11 10:37 ` [PR PATCH] [Updated] " fanyx
2022-10-11 10:38 ` fanyx
2022-10-11 10:39 ` fanyx
2022-10-14 10:18 ` [PR PATCH] [Updated] New package: hydrus-501 fanyx
2022-10-14 21:40 ` [PR REVIEW] New package: hydrus-502 paper42
2022-10-14 21:40 ` paper42
2022-10-14 21:40 ` paper42
2022-10-14 21:40 ` paper42
2022-10-14 21:40 ` paper42
2022-10-14 21:40 ` paper42
2022-10-14 21:40 ` paper42
2022-10-14 21:40 ` paper42
2022-10-14 23:43 ` fanyx
2022-10-14 23:44 ` fanyx
2022-10-14 23:46 ` fanyx
2022-10-14 23:46 ` fanyx
2022-10-15 10:30 ` [PR PATCH] [Updated] " fanyx
2022-10-15 10:31 ` [PR REVIEW] " fanyx
2022-10-15 10:32 ` fanyx
2022-10-15 10:33 ` fanyx
2022-10-15 10:40 ` [PR PATCH] [Updated] " fanyx
2022-10-15 10:42 ` [PR REVIEW] " fanyx
2022-10-15 10:42 ` fanyx
2022-10-15 10:44 ` [PR PATCH] [Updated] " fanyx
2022-10-16 12:24 ` fanyx
2022-10-17 7:00 ` fanyx
2022-10-17 7:02 ` fanyx
2022-10-25 13:01 ` fanyx
2022-10-27 13:27 ` [PR PATCH] [Updated] New package: hydrus-503 fanyx
2022-11-17 9:28 ` [PR PATCH] [Updated] New package: hydrus-504 fanyx
2022-11-17 10:32 ` [PR REVIEW] New package: hydrus-506 fanyx
2023-01-23 22:56 ` [PR PATCH] [Updated] " fanyx
2023-01-23 22:59 ` [PR PATCH] [Updated] New package: hydrus-513 fanyx
2023-01-30 11:19 ` fanyx
2023-01-30 11:19 ` fanyx
2023-02-09 9:16 ` fanyx
2023-04-26 12:58 ` fanyx
2023-04-28 8:01 ` [PR PATCH] [Updated] New package: hydrus-524 fanyx
2023-06-28 20:07 ` Duncaen [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=20230628200735.HamWln0F18TrJxOXRlJ5NbC4F2Q8Nsw7TB9lr9Jd-BQ@z \
--to=duncaen@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).