Github messages for voidlinux
 help / color / mirror / Atom feed
From: newbluemoon <newbluemoon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] tuxedo-keyboard: update to 3.1.2
Date: Sat, 14 Jan 2023 07:15:12 +0100	[thread overview]
Message-ID: <20230114061512.7t9aqMytcdlpBO89nLdZacbPPJ5riQLw1vW6H4T0sYE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41266@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]

There is an updated pull request by newbluemoon against master on the void-packages repository

https://github.com/newbluemoon/void-packages tuxedo-keyboard
https://github.com/void-linux/void-packages/pull/41266

tuxedo-keyboard: update to 3.1.2
<!-- 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)



A patch file from https://github.com/void-linux/void-packages/pull/41266.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-tuxedo-keyboard-41266.patch --]
[-- Type: text/x-diff, Size: 1159 bytes --]

From 521859969bb432c1322b4547fab6db95b55508f6 Mon Sep 17 00:00:00 2001
From: newbluemoon <blaumolch@mailbox.org>
Date: Sat, 24 Dec 2022 12:28:01 +0100
Subject: [PATCH] tuxedo-keyboard: update to 3.1.3

---
 srcpkgs/tuxedo-keyboard/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/tuxedo-keyboard/template b/srcpkgs/tuxedo-keyboard/template
index e9f528ef5ce7..d8e07dcf9e7a 100644
--- a/srcpkgs/tuxedo-keyboard/template
+++ b/srcpkgs/tuxedo-keyboard/template
@@ -1,6 +1,6 @@
 # Template file for 'tuxedo-keyboard'
 pkgname=tuxedo-keyboard
-version=3.1.1
+version=3.1.3
 revision=1
 depends="dkms"
 short_desc="TUXEDO kernel module drivers for keyboard & general hardware I/O"
@@ -8,7 +8,7 @@ maintainer="newbluemoon <blaumolch@mailbox.org>"
 license="GPL-3.0-or-later"
 homepage="https://github.com/tuxedocomputers/tuxedo-keyboard"
 distfiles="https://github.com/tuxedocomputers/tuxedo-keyboard/archive/v${version}.tar.gz"
-checksum=506de8c4076e42f51e2b0b6c0ffe48a3cc829d50a7c07f6a15a45e29fc3afc38
+checksum=6db8d0f9b1148c278b10f4f046e99370be1fa72aa8e3fc8db363168fe1b39e3e
 
 dkms_modules="tuxedo-keyboard ${version}"
 

  parent reply	other threads:[~2023-01-14  6:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-24 11:33 [PR PATCH] " newbluemoon
2023-01-01 12:08 ` [PR PATCH] [Updated] " newbluemoon
2023-01-14  0:48 ` [PR REVIEW] " classabbyamp
2023-01-14  6:15 ` newbluemoon [this message]
2023-01-15 11:13 ` [PR PATCH] [Merged]: tuxedo-keyboard: update to 3.1.3 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=20230114061512.7t9aqMytcdlpBO89nLdZacbPPJ5riQLw1vW6H4T0sYE@z \
    --to=newbluemoon@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).