From: Bnyro <Bnyro@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: libinput & libinput-debug-gui: update to 1.23.0 and add update-checks
Date: Sun, 09 Jul 2023 08:00:32 +0200 [thread overview]
Message-ID: <20230709060032.Iw02mKwWFYhd9cd_Q6Sbk7r-4_J7vxJLC8__LXTQiBQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44932@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 374 bytes --]
New comment by Bnyro on void-packages repository
https://github.com/void-linux/void-packages/pull/44932#issuecomment-1627615410
Comment:
I think it would be better if both commits for `libinput-debug-gui` are in a single commit, with a commit message like `libinput-debug-gui: update to 1.23.0`, because the added test dependencies are likely a side effect of the update.
next prev parent reply other threads:[~2023-07-09 6:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-09 0:31 [PR PATCH] " spiwocoal
2023-07-09 2:15 ` [PR PATCH] [Updated] " spiwocoal
2023-07-09 2:17 ` spiwocoal
2023-07-09 6:00 ` Bnyro
2023-07-09 6:00 ` Bnyro [this message]
2023-07-09 7:20 ` classabbyamp
2023-07-09 15:02 ` [PR PATCH] [Updated] " spiwocoal
2023-07-09 15:04 ` spiwocoal
2023-07-09 15:48 ` Bnyro
2023-07-09 15:50 ` Bnyro
2023-07-09 18:28 ` [PR PATCH] [Updated] " spiwocoal
2023-07-09 20:34 ` classabbyamp
2023-07-09 20:44 ` spiwocoal
2023-07-09 21:46 ` classabbyamp
2023-07-09 21:49 ` classabbyamp
2023-07-09 21:51 ` classabbyamp
2023-07-09 21:59 ` Bnyro
2023-07-09 22:00 ` Bnyro
2023-07-09 22:00 ` classabbyamp
2023-07-09 22:00 ` classabbyamp
2023-07-09 22:48 ` [PR PATCH] [Updated] " spiwocoal
2023-07-09 22:50 ` libinput-debug-gui: update to 1.23.0, add update-check spiwocoal
2023-07-09 22:52 ` classabbyamp
2023-07-09 22:57 ` [PR PATCH] [Closed]: " classabbyamp
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=20230709060032.Iw02mKwWFYhd9cd_Q6Sbk7r-4_J7vxJLC8__LXTQiBQ@z \
--to=bnyro@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).