From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: i3status-rust: update to 0.32.3
Date: Sun, 07 Jan 2024 06:14:50 +0100 [thread overview]
Message-ID: <20240107051450.eQPqYkr2ITLUGfa_eoVyGNKv4OUc6CGl0A0h6vNLqVA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47870@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 478 bytes --]
There's a merged pull request on the void-packages repository
i3status-rust: update to 0.32.3
https://github.com/void-linux/void-packages/pull/47870
Description:
Update the version of `i3status-rust`
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, amd64/x86_64-libc
- `xbps-src -Q pkg i3status-rust` completes with no errors
Glad to update anything else if needed!
next prev parent reply other threads:[~2024-01-07 5:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 6:03 [PR PATCH] " desertsagebrush
2023-12-22 6:11 ` [PR PATCH] [Updated] " desertsagebrush
2023-12-22 18:22 ` desertsagebrush
2023-12-23 13:33 ` [PR REVIEW] " classabbyamp
2023-12-23 20:49 ` desertsagebrush
2023-12-23 20:52 ` desertsagebrush
2023-12-23 20:54 ` desertsagebrush
2023-12-23 21:09 ` classabbyamp
2023-12-23 21:13 ` classabbyamp
2023-12-25 21:57 ` desertsagebrush
2023-12-25 22:03 ` desertsagebrush
2023-12-25 22:09 ` desertsagebrush
2023-12-25 22:10 ` desertsagebrush
2023-12-25 22:15 ` desertsagebrush
2023-12-25 22:30 ` desertsagebrush
2023-12-25 22:34 ` desertsagebrush
2023-12-25 22:46 ` [PR PATCH] [Updated] " desertsagebrush
2023-12-25 22:48 ` desertsagebrush
2023-12-25 22:49 ` [PR REVIEW] " desertsagebrush
2023-12-25 22:51 ` desertsagebrush
2023-12-31 19:37 ` desertsagebrush
2024-01-07 4:56 ` [PR PATCH] [Updated] " classabbyamp
2024-01-07 4:57 ` classabbyamp
2024-01-07 4:57 ` classabbyamp
2024-01-07 5:14 ` classabbyamp [this message]
2024-01-13 19:07 ` desertsagebrush
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=20240107051450.eQPqYkr2ITLUGfa_eoVyGNKv4OUc6CGl0A0h6vNLqVA@z \
--to=classabbyamp@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).