From: JohnGebbie <JohnGebbie@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New package: ydotool-1.0.1
Date: Sat, 22 Oct 2022 21:50:16 +0200 [thread overview]
Message-ID: <20221022195016.aRR1OYaOKlrc1wvdMQq2lURK3GAqXZgFk1XhXib8Nk8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39920@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]
There's a closed pull request on the void-packages repository
New package: ydotool-1.0.1
https://github.com/void-linux/void-packages/pull/39920
Description:
#### 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**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
- I cross built it for i686 and tested it on my laptop.
- I cross built it for aarch64-musl and tested it on my Raspberry Pi 4.
I started with https://github.com/void-linux/void-packages/pull/31237
Closes https://github.com/void-linux/void-packages/issues/31163
Sorry this is a continuation of https://github.com/void-linux/void-packages/pull/38268. I did a bad push that automatically closed the pull request, and then a force push to fix it but github won't let me reopen it because I force pushed when it was closed :( I was just trying to add a log/run to the service and update the branch.
The package is ready. I use it to type (with my voice) so I've been using it a lot.
next prev parent reply other threads:[~2022-10-22 19:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 20:19 [PR PATCH] " JohnGebbie
2022-10-12 20:37 ` paper42
2022-10-12 20:40 ` [PR REVIEW] " paper42
2022-10-12 22:13 ` [PR PATCH] [Updated] " JohnGebbie
2022-10-12 22:17 ` [PR REVIEW] " JohnGebbie
2022-10-14 8:46 ` JohnGebbie
2022-10-14 21:53 ` [PR REVIEW] " paper42
2022-10-14 22:05 ` paper42
2022-10-15 9:18 ` [PR PATCH] [Updated] " JohnGebbie
2022-10-15 10:47 ` JohnGebbie
2022-10-15 11:10 ` JohnGebbie
2022-10-15 11:14 ` JohnGebbie
2022-10-15 11:23 ` [PR REVIEW] " JohnGebbie
2022-10-16 10:06 ` [PR PATCH] [Updated] " JohnGebbie
2022-10-16 10:08 ` JohnGebbie
2022-10-17 19:39 ` JohnGebbie
2022-10-20 10:14 ` [PR REVIEW] " sgn
2022-10-20 10:17 ` sgn
2022-10-22 19:50 ` JohnGebbie
2022-10-22 19:50 ` JohnGebbie [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-28 0:27 [PR PATCH] " Newchair2644
2022-12-28 16:32 ` [PR PATCH] [Closed]: " Newchair2644
2022-07-25 12:49 [PR PATCH] " JohnGebbie
2022-08-08 19:28 ` [PR PATCH] [Closed]: " JohnGebbie
2022-10-12 19:31 ` JohnGebbie
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=20221022195016.aRR1OYaOKlrc1wvdMQq2lURK3GAqXZgFk1XhXib8Nk8@z \
--to=johngebbie@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).