From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: New package: webhook-2.8.0
Date: Wed, 16 Feb 2022 00:46:39 +0100 [thread overview]
Message-ID: <20220215234639.ePkuiu9KB9pephChiQcbNNKjN7dmqk_U2TK-HxexY7M@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32813@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1456 bytes --]
There's a merged pull request on the void-packages repository
New package: webhook-2.8.0
https://github.com/void-linux/void-packages/pull/32813
Description:
<!-- Mark items with [x] where applicable -->
#### General
- [x] 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.)
- [x] I built this PR locally for my native architecture, (x86_64-glibc)
- [x] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [x] aarch64-musl (cross)
- [x] armv7l (cross)
- [x] armv6l-musl (cross)
prev parent reply other threads:[~2022-02-15 23:46 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 5:01 [PR PATCH] " classabbyamp
2021-09-03 5:04 ` classabbyamp
2021-09-03 5:05 ` classabbyamp
2021-09-04 2:10 ` [PR PATCH] [Updated] " classabbyamp
2021-09-04 2:12 ` classabbyamp
2021-09-05 22:17 ` [PR PATCH] [Updated] " classabbyamp
2021-09-06 17:58 ` [PR REVIEW] " ericonr
2021-09-06 17:58 ` ericonr
2021-09-06 17:58 ` ericonr
2021-09-06 17:58 ` ericonr
2021-09-06 17:58 ` ericonr
2021-09-06 19:35 ` classabbyamp
2021-09-06 19:44 ` classabbyamp
2021-09-06 22:10 ` [PR PATCH] [Updated] " classabbyamp
2021-09-06 22:19 ` classabbyamp
2021-10-05 2:19 ` classabbyamp
2021-10-05 2:20 ` classabbyamp
2021-10-05 2:23 ` [PR REVIEW] " classabbyamp
2021-10-05 2:30 ` [PR PATCH] [Updated] " classabbyamp
2021-10-05 2:31 ` classabbyamp
2021-10-05 7:43 ` [PR REVIEW] " adnanh
2021-10-05 15:02 ` [PR PATCH] [Updated] " classabbyamp
2021-11-05 23:22 ` classabbyamp
2021-11-13 3:40 ` classabbyamp
2022-02-04 18:00 ` classabbyamp
2022-02-15 23:22 ` classabbyamp
2022-02-15 23:29 ` classabbyamp
2022-02-15 23:36 ` [PR REVIEW] " paper42
2022-02-15 23:36 ` classabbyamp
2022-02-15 23:37 ` classabbyamp
2022-02-15 23:46 ` 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=20220215234639.ePkuiu9KB9pephChiQcbNNKjN7dmqk_U2TK-HxexY7M@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).