Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: calibre: update to 5.14.0.
Date: Tue, 06 Apr 2021 14:35:11 +0200	[thread overview]
Message-ID: <20210406123511.sA0_6_dIMEGBpX5MVBPMa-QZ3QlZW39juCO1GowOFsM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29744@inbox.vuxu.org>

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

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

calibre: update to 5.14.0.
https://github.com/void-linux/void-packages/pull/29744

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?
- [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
-->


      parent reply	other threads:[~2021-04-06 12:35 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-25  8:38 [PR PATCH] calibre: update to 5.13.0 skmpz
2021-03-25  8:42 ` [PR PATCH] [Updated] " skmpz
2021-03-25  8:42 ` skmpz
2021-03-25  8:49 ` [PR PATCH] [Updated] " skmpz
2021-03-25  8:56 ` skmpz
2021-03-25 12:30 ` ericonr
2021-03-25 17:18 ` [PR PATCH] [Updated] " skmpz
2021-03-25 17:20 ` skmpz
2021-03-25 17:20 ` skmpz
2021-03-25 17:25 ` skmpz
2021-03-25 17:25 ` skmpz
2021-04-01  2:34 ` backerman
2021-04-01  4:07 ` backerman
2021-04-03 19:12 ` [PR REVIEW] " ericonr
2021-04-03 19:12 ` ericonr
2021-04-03 19:12 ` ericonr
2021-04-04  7:39 ` skmpz
2021-04-04  7:39 ` [PR REVIEW] " skmpz
2021-04-04  7:39 ` skmpz
2021-04-04  8:16 ` [PR REVIEW] " FollieHiyuki
2021-04-04 10:42 ` skmpz
2021-04-04 10:42 ` skmpz
2021-04-04 11:21 ` FollieHiyuki
2021-04-04 11:33 ` FollieHiyuki
2021-04-04 11:52 ` [PR REVIEW] " skmpz
2021-04-04 11:52 ` skmpz
2021-04-04 11:57 ` skmpz
2021-04-04 13:16 ` [PR PATCH] [Updated] " skmpz
2021-04-04 13:34 ` calibre: update to 5.14.0 skmpz
2021-04-04 13:36 ` skmpz
2021-04-04 23:55 ` ericonr
2021-04-05  1:20 ` [PR REVIEW] " ahesford
2021-04-05  2:35 ` ericonr
2021-04-05  2:36 ` ericonr
2021-04-05  4:21 ` [PR PATCH] [Updated] " skmpz
2021-04-05  4:25 ` [PR REVIEW] " skmpz
2021-04-05  9:54 ` ahesford
2021-04-05  9:54 ` ahesford
2021-04-05  9:54 ` ahesford
2021-04-05 10:06 ` skmpz
2021-04-05 10:32 ` skmpz
2021-04-05 10:36 ` skmpz
2021-04-05 13:26 ` [PR REVIEW] [WIP] " ericonr
2021-04-06  4:37 ` [PR PATCH] [Updated] " skmpz
2021-04-06  4:57 ` skmpz
2021-04-06  5:11 ` skmpz
2021-04-06  5:23 ` skmpz
2021-04-06  5:24 ` skmpz
2021-04-06  5:39 ` skmpz
2021-04-06 11:41 ` ericonr
2021-04-06 11:46 ` skmpz
2021-04-06 11:51 ` ericonr
2021-04-06 11:51 ` ericonr
2021-04-06 11:59 ` [PR PATCH] [Updated] " skmpz
2021-04-06 12:00 ` skmpz
2021-04-06 12:35 ` ericonr
2021-04-06 12:35 ` ericonr [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=20210406123511.sA0_6_dIMEGBpX5MVBPMa-QZ3QlZW39juCO1GowOFsM@z \
    --to=ericonr@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).