From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New package: logiops-0.2.3
Date: Wed, 28 Jun 2023 19:49:02 +0200 [thread overview]
Message-ID: <20230628174902.prC2ZEUUiKOg5tGrK-79kvSCj0SxRIsx6gBKKDb_Vuk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42849@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
There's a closed pull request on the void-packages repository
New package: logiops-0.2.3
https://github.com/void-linux/void-packages/pull/42849
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**
<!-- 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, (x86_64-glibc)
next prev parent reply other threads:[~2023-06-28 17:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-18 21:58 [PR PATCH] " T0mstone
2023-03-19 22:42 ` [PR PATCH] [Updated] " T0mstone
2023-03-19 22:44 ` T0mstone
2023-03-26 18:55 ` T0mstone
2023-06-25 2:13 ` github-actions
2023-06-25 18:53 ` [PR REVIEW] " Duncaen
2023-06-25 18:56 ` Duncaen
2023-06-28 17:21 ` [PR PATCH] [Updated] " T0mstone
2023-06-28 17:23 ` T0mstone
2023-06-28 17:49 ` Duncaen [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-08 22:12 [PR PATCH] " Owenlaw222
2023-02-22 2:01 ` [PR PATCH] [Closed]: " github-actions
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=20230628174902.prC2ZEUUiKOg5tGrK-79kvSCj0SxRIsx6gBKKDb_Vuk@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).