From: bitterhalt <bitterhalt@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: i3bar-river-1.0.1
Date: Mon, 21 Oct 2024 17:00:44 +0200 [thread overview]
Message-ID: <20241021150044.4A1E32F10E@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-52665@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 766 bytes --]
There is an updated pull request by bitterhalt against master on the void-packages repository
https://github.com/bitterhalt/void-packages i3bar-river
https://github.com/void-linux/void-packages/pull/52665
New package: i3bar-river-1.0.1
#### 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**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
- I built this PR locally for these architectures:
- x86_64-glibc
A patch file from https://github.com/void-linux/void-packages/pull/52665.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-i3bar-river-52665.patch --]
[-- Type: text/x-diff, Size: 0 bytes --]
next prev parent reply other threads:[~2024-10-21 15:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 14:22 [PR PATCH] " bitterhalt
2024-10-17 15:01 ` [PR PATCH] [Updated] " bitterhalt
2024-10-17 15:05 ` bitterhalt
2024-10-21 14:58 ` bitterhalt
2024-10-21 15:00 ` [PR PATCH] [Closed]: " bitterhalt
2024-10-21 15:00 ` bitterhalt [this message]
2024-10-23 12:00 [PR PATCH] " bitterhalt
2024-10-23 12:14 ` [PR PATCH] [Updated] " bitterhalt
2024-10-23 17:11 ` bitterhalt
2024-10-23 17:32 ` bitterhalt
2024-10-23 17:36 ` bitterhalt
2024-10-23 17:55 ` bitterhalt
2024-10-30 21:04 ` bitterhalt
2024-10-30 21:15 ` bitterhalt
2024-11-20 13:29 ` bitterhalt
2024-11-20 13:31 ` bitterhalt
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=20241021150044.4A1E32F10E@inbox.vuxu.org \
--to=bitterhalt@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).