From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: sc-controller: move to a python3 fork, update to 0.4.8.6.
Date: Sat, 12 Feb 2022 22:37:22 +0100 [thread overview]
Message-ID: <20220212213722.IJnFIULT9PX2IbqVAK52uKLDdmk5XEa41O4L-1ewCl8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34912@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 369 bytes --]
There's a merged pull request on the void-packages repository
sc-controller: move to a python3 fork, update to 0.4.8.6.
https://github.com/void-linux/void-packages/pull/34912
Description:
#### Testing the changes
- I tested the changes in this PR: **briefly**
I can't test this, because I don't have a steam controller, so I would appreciate some help. @Hnaguski
next prev parent reply other threads:[~2022-02-12 21:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 20:45 [PR PATCH] " paper42
2022-01-06 23:35 ` Hnaguski
2022-02-08 3:42 ` Hnaguski
2022-02-12 21:37 ` paper42 [this message]
2022-02-12 21:38 ` paper42
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=20220212213722.IJnFIULT9PX2IbqVAK52uKLDdmk5XEa41O4L-1ewCl8@z \
--to=paper42@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).