From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: gpgme: fix returning incorrect error codes
Date: Tue, 18 Oct 2022 11:50:06 +0200 [thread overview]
Message-ID: <20221018095006.lB_Tj7ngGO5Eum1gYgi20ZRtKQEwEY7V6nrqFmGd-6w@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38825@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]
There's a merged pull request on the void-packages repository
gpgme: fix returning incorrect error codes
https://github.com/void-linux/void-packages/pull/38825
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
I tested gpgme with pacman and haven't noticed any issues.
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
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
-->
prev parent reply other threads:[~2022-10-18 9:50 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 5:58 [PR PATCH] gpgme: update to 1.18.0 oreo639
2022-08-22 6:07 ` [PR PATCH] [Updated] " oreo639
2022-08-22 6:12 ` oreo639
2022-08-22 7:22 ` oreo639
2022-09-08 2:27 ` classabbyamp
2022-09-08 2:28 ` classabbyamp
2022-09-08 2:28 ` classabbyamp
2022-09-08 21:39 ` [PR PATCH] [Updated] " oreo639
2022-09-08 22:36 ` oreo639
2022-09-08 22:52 ` oreo639
2022-09-09 0:56 ` oreo639
2022-09-09 2:27 ` oreo639
2022-09-09 2:35 ` oreo639
2022-09-14 10:56 ` [PR PATCH] [Updated] " oreo639
2022-09-14 11:07 ` oreo639
2022-09-14 11:20 ` oreo639
2022-09-14 11:45 ` oreo639
2022-09-14 12:11 ` oreo639
2022-09-14 12:27 ` oreo639
2022-09-14 19:43 ` oreo639
2022-09-14 20:43 ` oreo639
2022-09-14 20:49 ` oreo639
2022-09-15 7:32 ` oreo639
2022-10-04 9:05 ` oreo639
2022-10-18 3:38 ` classabbyamp
2022-10-18 3:38 ` [PR PATCH] [Closed]: " classabbyamp
2022-10-18 4:17 ` oreo639
2022-10-18 4:19 ` classabbyamp
2022-10-18 4:21 ` [PR PATCH] [Updated] " oreo639
2022-10-18 4:21 ` oreo639
2022-10-18 4:22 ` [PR PATCH] [Updated] gpgme: fix returning incorrect error codes oreo639
2022-10-18 4:24 ` oreo639
2022-10-18 4:31 ` classabbyamp
2022-10-18 4:33 ` oreo639
2022-10-18 4:33 ` oreo639
2022-10-18 7:07 ` [PR PATCH] [Updated] " oreo639
2022-10-18 8:43 ` oreo639
2022-10-18 9:50 ` classabbyamp [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=20221018095006.lB_Tj7ngGO5Eum1gYgi20ZRtKQEwEY7V6nrqFmGd-6w@z \
--to=classabbyamp@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).