Github messages for voidlinux
 help / color / mirror / Atom feed
From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: poppler: update to 22.07.0
Date: Wed, 06 Jul 2022 10:50:58 +0200	[thread overview]
Message-ID: <20220706085058.EMUwDfSd0YcNCimSEXLziZS0D7nLqH2IWywprPXCeIM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36351@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]

There's a merged pull request on the void-packages repository

poppler: update to 22.07.0
https://github.com/void-linux/void-packages/pull/36351

Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **briefly**

<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->

<!-- 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, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


      parent reply	other threads:[~2022-07-06  8:50 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-26  1:37 [PR PATCH] poppler: update to 22.03.0 oreo639
2022-03-26  1:39 ` [PR PATCH] [Updated] " oreo639
2022-03-26  3:40 ` oreo639
2022-03-26  3:41 ` oreo639
2022-03-26  3:42 ` [PR PATCH] [Updated] " oreo639
2022-03-26  3:42 ` oreo639
2022-03-26  4:03 ` [PR PATCH] [Updated] " oreo639
2022-03-26  5:21 ` oreo639
2022-03-26  5:48 ` oreo639
2022-03-26  6:21 ` oreo639
2022-03-26 17:54 ` oreo639
2022-03-26 17:59 ` oreo639
2022-03-26 19:03 ` oreo639
2022-03-26 19:30 ` oreo639
2022-03-26 19:30 ` oreo639
2022-04-17  8:12 ` oreo639
2022-04-17  8:14 ` oreo639
2022-04-17  8:35 ` [PR PATCH] [Updated] " oreo639
2022-04-17  8:52 ` [PR PATCH] [Updated] poppler: update to 22.04.0 oreo639
2022-04-17  9:29 ` oreo639
2022-04-17  9:31 ` oreo639
2022-04-17  9:35 ` oreo639
2022-04-17 10:22 ` oreo639
2022-04-17 10:45 ` oreo639
2022-04-17 10:46 ` oreo639
2022-04-17 10:47 ` oreo639
2022-04-17 10:55 ` oreo639
2022-04-17 23:07 ` [PR PATCH] [Updated] " oreo639
2022-04-18 23:47 ` oreo639
2022-05-01  2:03 ` oreo639
2022-05-01  2:05 ` oreo639
2022-05-12  4:19 ` oreo639
2022-05-16 21:43 ` oreo639
2022-06-11 23:10 ` oreo639
2022-06-17  0:05 ` [PR PATCH] [Updated] poppler: update to 22.06.0 oreo639
2022-06-17  0:51 ` oreo639
2022-06-17  1:40 ` classabbyamp
2022-06-17  4:53 ` oreo639
2022-06-18 23:59 ` oreo639
2022-06-19  0:02 ` oreo639
2022-06-19  0:02 ` oreo639
2022-06-19  0:04 ` oreo639
2022-06-19  0:05 ` [PR PATCH] [Updated] " oreo639
2022-06-19  0:06 ` oreo639
2022-06-19  0:06 ` oreo639
2022-06-19  0:10 ` oreo639
2022-06-19  0:11 ` oreo639
2022-06-19  0:37 ` oreo639
2022-07-05 10:47 ` paper42
2022-07-05 18:26 ` oreo639
2022-07-05 18:29 ` oreo639
2022-07-05 18:30 ` oreo639
2022-07-05 18:31 ` oreo639
2022-07-05 18:42 ` oreo639
2022-07-05 18:47 ` oreo639
2022-07-05 19:38 ` oreo639
2022-07-05 23:12 ` [PR PATCH] [Updated] " oreo639
2022-07-05 23:13 ` oreo639
2022-07-05 23:26 ` oreo639
2022-07-05 23:38 ` oreo639
2022-07-05 23:58 ` [PR PATCH] [Updated] poppler: update to 22.07.0 oreo639
2022-07-06  7:39 ` oreo639
2022-07-06  7:39 ` oreo639
2022-07-06  7:40 ` oreo639
2022-07-06  8:50 ` paper42 [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=20220706085058.EMUwDfSd0YcNCimSEXLziZS0D7nLqH2IWywprPXCeIM@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).