From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: New package: wiki-tui-0.8.2
Date: Mon, 14 Aug 2023 07:15:12 +0200 [thread overview]
Message-ID: <20230814051512.p_fQVq1_5wwKRBKPB3F8TORieAfbNW5GYXwmp1gFGuk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45438@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]
There's a merged pull request on the void-packages repository
New package: wiki-tui-0.8.2
https://github.com/void-linux/void-packages/pull/45438
Description:
#### 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**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-musl)
- I built this PR locally for these architectures (crossbuilds, **both glibc and musl** where possible):
- x86_64
- i686
- aarch64
- armv7l
- armv6l
*This is my first package for any distribution. I'm particularly eager to suggestions if I got anything wrong! (Specifically, I'm not sure if I needed to add compilation options, since the package allows [multiple possible ncurses-like backends](https://builditluc.github.io/wiki-tui/0.8/getting-started/installation/#cargo). I couldn't find anything about having mutually exclusive options in the manual.)*
prev parent reply other threads:[~2023-08-14 5:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-05 18:46 [PR PATCH] New package: wiki-tui-0.8.1 ethamck
2023-08-06 3:25 ` classabbyamp
2023-08-09 23:57 ` ethamck
2023-08-09 23:59 ` ethamck
2023-08-12 14:13 ` [PR PATCH] [Updated] " ethamck
2023-08-12 22:12 ` [PR PATCH] [Updated] New package: wiki-tui-0.8.2 ethamck
2023-08-13 1:29 ` ethamck
2023-08-14 5:15 ` classabbyamp [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=20230814051512.p_fQVq1_5wwKRBKPB3F8TORieAfbNW5GYXwmp1gFGuk@z \
--to=classabbyamp@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).