From: vutunganh <vutunganh@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New package: mullvad-vpn-2021.6
Date: Sun, 02 Jan 2022 10:10:23 +0100 [thread overview]
Message-ID: <20220102091023.eE1VgU9aU3xN44b_QbFzpYXkes8tMpgpMYI_00H1DXQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34720@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]
There's a closed pull request on the void-packages repository
New package: mullvad-vpn-2021.6
https://github.com/void-linux/void-packages/pull/34720
Description:
Since this packages precompiled binaries (for Debian), maybe the package name should be renamed to something like `mullvad-vpn-bin`. I am not sure what the procedure is, please let me know.
#### Testing the changes
- I tested the changes in this PR: **YES**
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](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)
Resolves https://github.com/void-linux/void-packages/issues/21154.
prev parent reply other threads:[~2022-01-02 9:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 16:28 [PR PATCH] " vutunganh
2021-12-30 14:17 ` sgn
2022-01-02 9:10 ` vutunganh
2022-01-02 9:10 ` vutunganh [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=20220102091023.eE1VgU9aU3xN44b_QbFzpYXkes8tMpgpMYI_00H1DXQ@z \
--to=vutunganh@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).