From: Piraty <Piraty@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: New package: drivestrike-2.1.20
Date: Sun, 09 Apr 2023 22:06:45 +0200 [thread overview]
Message-ID: <20230409200645.QrcKxxw2I_E2-OKZvSYIO3iDIPDZsMyhJDPcrShvhhM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38917@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1317 bytes --]
There's a merged pull request on the void-packages repository
New package: drivestrike-2.1.20
https://github.com/void-linux/void-packages/pull/38917
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
Not sure if this is interesting for anyone here, but we have to deploy this onto our machines for work, so I created this template to install it on my work laptop. EULA says no copies except for subscribers installing it onto their systems, so `restricted` it is.
#### Testing the changes
- I tested the changes in this PR: **YES**
#### 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, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
prev parent reply other threads:[~2023-04-09 20:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 8:00 [PR PATCH] " jcgruenhage
2022-08-26 8:59 ` [PR PATCH] [Updated] " jcgruenhage
2022-11-25 17:11 ` madonius
2022-11-26 16:06 ` jcgruenhage
2022-11-27 13:48 ` [PR PATCH] [Updated] " jcgruenhage
2022-11-27 13:49 ` jcgruenhage
2022-12-14 0:19 ` [PR REVIEW] New package: drivestrike-2.1.21 Piraty
2022-12-14 0:20 ` Piraty
2022-12-14 7:55 ` jcgruenhage
2022-12-14 8:07 ` [PR PATCH] [Updated] " jcgruenhage
2023-03-05 22:33 ` [PR REVIEW] " Piraty
2023-03-06 20:19 ` [PR PATCH] [Updated] " jcgruenhage
2023-04-05 10:00 ` [PR PATCH] [Updated] New package: drivestrike-2.1.20 jcgruenhage
2023-04-09 20:06 ` Piraty [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=20230409200645.QrcKxxw2I_E2-OKZvSYIO3iDIPDZsMyhJDPcrShvhhM@z \
--to=piraty@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).