From: shenlebantongying <shenlebantongying@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] goldendict-ng: initial upload
Date: Tue, 24 Oct 2023 07:13:37 +0200 [thread overview]
Message-ID: <20231024051337.I-ViFgJVMU83d1UfEUSxDwd_IaPa9d3u8YU_LE6sja0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44234@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 918 bytes --]
There is an updated pull request by shenlebantongying against master on the void-packages repository
https://github.com/shenlebantongying/void-packages master
https://github.com/void-linux/void-packages/pull/44234
goldendict-ng: initial upload
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### 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, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/44234.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-44234.patch --]
[-- Type: text/x-diff, Size: 0 bytes --]
next prev parent reply other threads:[~2023-10-24 5:13 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 23:23 [PR PATCH] " shenlebantongying
2023-06-03 0:09 ` classabbyamp
2023-06-03 0:09 ` [PR REVIEW] " classabbyamp
2023-06-03 0:10 ` classabbyamp
2023-06-03 0:15 ` [PR PATCH] [Updated] " shenlebantongying
2023-06-03 0:16 ` shenlebantongying
2023-06-03 0:16 ` shenlebantongying
2023-06-03 0:18 ` [PR PATCH] [Updated] " shenlebantongying
2023-06-03 0:27 ` shenlebantongying
2023-06-03 0:30 ` shenlebantongying
2023-06-03 0:36 ` shenlebantongying
2023-06-03 0:40 ` shenlebantongying
2023-06-03 0:41 ` shenlebantongying
2023-06-03 0:52 ` [PR PATCH] [Updated] " shenlebantongying
2023-06-03 0:59 ` shenlebantongying
2023-06-03 1:15 ` [PR PATCH] [Updated] " shenlebantongying
2023-06-03 1:17 ` shenlebantongying
2023-06-03 1:17 ` shenlebantongying
2023-06-03 1:22 ` shenlebantongying
2023-06-03 1:27 ` shenlebantongying
2023-06-03 2:16 ` shenlebantongying
2023-09-02 1:43 ` github-actions
2023-10-20 12:56 ` thangisme
2023-10-20 19:12 ` classabbyamp
2023-10-20 19:13 ` [PR REVIEW] " classabbyamp
2023-10-20 19:38 ` [PR PATCH] [Updated] " shenlebantongying
2023-10-20 19:38 ` shenlebantongying
2023-10-24 4:26 ` [PR PATCH] [Updated] " shenlebantongying
2023-10-24 5:00 ` shenlebantongying
2023-10-24 5:13 ` [PR PATCH] [Closed]: " shenlebantongying
2023-10-24 5:13 ` shenlebantongying [this message]
2023-10-24 5:22 ` shenlebantongying
2023-10-24 7:08 ` [PR PATCH] [Updated] " shenlebantongying
2023-10-24 7:08 ` shenlebantongying
2023-10-24 7:08 ` shenlebantongying
2023-10-24 7:09 ` shenlebantongying
2023-10-24 7:09 ` shenlebantongying
2023-10-24 7:21 ` [PR PATCH] [Updated] " shenlebantongying
2023-10-24 7:22 ` shenlebantongying
2023-10-24 12:46 ` classabbyamp
2023-10-24 16:36 ` [PR PATCH] [Updated] " shenlebantongying
2023-10-24 17:17 ` shenlebantongying
2023-10-24 17:21 ` shenlebantongying
2023-10-24 17:27 ` shenlebantongying
2023-10-24 18:28 ` [PR PATCH] [Updated] " shenlebantongying
2023-10-24 18:29 ` shenlebantongying
2023-10-25 20:07 ` shenlebantongying
2023-10-25 20:07 ` shenlebantongying
2023-10-29 3:07 ` shenlebantongying
2023-10-29 3:07 ` shenlebantongying
2023-12-12 23:06 ` [PR PATCH] [Closed]: " shenlebantongying
2023-12-12 23:06 ` shenlebantongying
2023-12-12 23:11 ` shenlebantongying
2024-05-20 3:21 ` darkralts
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=20231024051337.I-ViFgJVMU83d1UfEUSxDwd_IaPa9d3u8YU_LE6sja0@z \
--to=shenlebantongying@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).