From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: New package: pdfarranger-1.10.1
Date: Wed, 10 Jan 2024 12:39:52 +0100 [thread overview]
Message-ID: <20240110113952.Zu5AycDiZZMnNsp4d4PztqtZR-kUIB3I2qa4tPdOz0o@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40541@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 538 bytes --]
There's a merged pull request on the void-packages repository
New package: pdfarranger-1.10.1
https://github.com/void-linux/void-packages/pull/40541
Description:
closes #40138
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
prev parent reply other threads:[~2024-01-10 11:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 17:19 [PR PATCH] New package: pdfarranger-1.9.1 Eloitor
2022-12-29 13:41 ` [PR PATCH] [Updated] " Eloitor
2023-03-30 1:56 ` New package: pdfarranger-1.9.2 github-actions
2023-03-30 10:23 ` Eloitor
2023-04-04 15:55 ` [PR PATCH] [Updated] " Eloitor
2023-04-04 18:50 ` [PR REVIEW] " paper42
2023-04-04 18:50 ` paper42
2023-04-04 22:07 ` [PR PATCH] [Updated] " Eloitor
2023-04-04 22:10 ` [PR REVIEW] " Eloitor
2023-06-06 11:45 ` ahesford
2023-06-16 20:11 ` gc-user
2023-09-02 22:05 ` [PR PATCH] [Updated] " Eloitor
2023-12-02 1:45 ` New package: pdfarranger-1.10.0 github-actions
2023-12-02 14:45 ` [PR PATCH] [Updated] " Eloitor
2023-12-30 21:08 ` [PR PATCH] [Updated] New package: pdfarranger-1.10.1 Eloitor
2024-01-10 7:59 ` Eloitor
2024-01-10 11:39 ` ahesford [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=20240110113952.Zu5AycDiZZMnNsp4d4PztqtZR-kUIB3I2qa4tPdOz0o@z \
--to=ahesford@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).