From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New package: dpp-10.0.23_1
Date: Tue, 27 Jun 2023 13:55:34 +0200 [thread overview]
Message-ID: <20230627115534.Tt4Ca13tjivlCGR-6QE76gWScMldJVBSec447gn0zwU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42521@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 907 bytes --]
There's a closed pull request on the void-packages repository
New package: dpp-10.0.23_1
https://github.com/void-linux/void-packages/pull/42521
Description:
#### 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-LIBC)
#### About
Libdpp is a C++ lightweight and scalable Discord library. With full support for all of the Discord API, we believe we're ready to be put into the Void Linux repositories for use by our users. We've done our best to comply with the guidelines, however please let me know if there are any improvements I could make to this PR.
#### Notes
Previous PRs (by others): #38601, #37554
prev parent reply other threads:[~2023-06-27 11:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 7:59 [PR PATCH] New package: libdpp-10.0.23_1 OoLunar
2023-03-02 21:50 ` [PR PATCH] [Updated] " OoLunar
2023-03-03 2:46 ` OoLunar
2023-03-03 3:30 ` OoLunar
2023-03-03 17:23 ` [PR REVIEW] New package: dpp-10.0.23_1 paper42
2023-03-03 17:26 ` OoLunar
2023-03-03 17:35 ` paper42
2023-03-04 1:48 ` OoLunar
2023-03-04 1:49 ` OoLunar
2023-03-04 22:20 ` paper42
2023-03-06 2:50 ` OoLunar
2023-03-06 2:52 ` [PR PATCH] [Updated] " OoLunar
2023-03-06 5:06 ` [PR REVIEW] " paper42
2023-03-06 5:17 ` [PR PATCH] [Updated] " OoLunar
2023-04-01 19:44 ` OoLunar
2023-06-27 11:55 ` Duncaen [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=20230627115534.Tt4Ca13tjivlCGR-6QE76gWScMldJVBSec447gn0zwU@z \
--to=duncaen@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).