From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: ibus-libpinyin: update to 1.15.0
Date: Sun, 05 Feb 2023 02:29:20 +0100 [thread overview]
Message-ID: <20230205012920.htGSaPVNmLGUfBz_Dfu1HywTfPRY7oFNP3K9iQNaW54@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42031@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 959 bytes --]
There's a merged pull request on the void-packages repository
ibus-libpinyin: update to 1.15.0
https://github.com/void-linux/void-packages/pull/42031
Description:
<!-- 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**|**NO**
-->
<!-- 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)
prev parent reply other threads:[~2023-02-05 1:29 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 11:25 [PR PATCH] " LMFuture-Me
2023-02-02 11:37 ` [PR REVIEW] " sgn
2023-02-02 11:37 ` sgn
2023-02-02 11:37 ` sgn
2023-02-02 11:37 ` sgn
2023-02-02 11:38 ` [PR PATCH] [Updated] " sgn
2023-02-02 11:38 ` sgn
2023-02-02 11:39 ` sgn
2023-02-02 11:39 ` sgn
2023-02-02 11:43 ` LMFuture-Me
2023-02-02 11:49 ` LMFuture-Me
2023-02-02 11:49 ` LMFuture-Me
2023-02-02 12:10 ` [PR PATCH] [Updated] " sgn
2023-02-02 12:13 ` sgn
2023-02-02 12:14 ` sgn
2023-02-02 12:16 ` [PR PATCH] [Updated] " sgn
2023-02-02 12:16 ` LMFuture-Me
2023-02-02 12:16 ` [PR PATCH] [Closed]: " LMFuture-Me
2023-02-02 12:16 ` LMFuture-Me
2023-02-02 12:17 ` LMFuture-Me
2023-02-02 12:31 ` [PR PATCH] [Updated] " LMFuture-Me
2023-02-02 16:00 ` sgn
2023-02-02 16:01 ` sgn
2023-02-02 23:45 ` [PR PATCH] [Updated] " LMFuture-Me
2023-02-02 23:51 ` LMFuture-Me
2023-02-02 23:52 ` LMFuture-Me
2023-02-02 23:52 ` LMFuture-Me
2023-02-02 23:54 ` LMFuture-Me
2023-02-03 0:09 ` LMFuture-Me
2023-02-03 1:49 ` LMFuture-Me
2023-02-03 4:05 ` [PR PATCH] [Updated] " sgn
2023-02-05 1:29 ` sgn [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=20230205012920.htGSaPVNmLGUfBz_Dfu1HywTfPRY7oFNP3K9iQNaW54@z \
--to=sgn@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).