From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: New packages: rbw-1.4.3, rofi-rbw-1.0.0
Date: Mon, 20 Jun 2022 20:24:40 +0200 [thread overview]
Message-ID: <20220620182440.VoCLSopuW4oo5rU0pJa8FbpawGlY0PfHrK5WWQhX1MU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32355@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1832 bytes --]
There's a merged pull request on the void-packages repository
New packages: rbw-1.4.3, rofi-rbw-1.0.0
https://github.com/void-linux/void-packages/pull/32355
Description:
<!-- Mark items with [x] where applicable -->
#### General
- [x] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [x] I built this PR locally for my native architecture, (x86_64-musl)
- [x] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [x] aarch64-musl
- [x] armv7l
- [x] armv7l-musl
- [x] armv6l
- [x] armv6l-musl
Closes #28973
#### Note:
Not sure whether to include the shell scripts in the [bin](https://git.tozt.net/rbw/tree/bin) directory, as they aren't installed on [Arch](https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=rbw) and are behind feature flags on [Nix](https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/security/rbw/default.nix#L77).
prev parent reply other threads:[~2022-06-20 18:24 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 23:05 [PR PATCH] New package: rbw-1.3.0 ram02z
2021-08-06 0:17 ` [PR PATCH] [Updated] " ram02z
2021-08-06 11:50 ` ram02z
2021-08-06 11:53 ` ram02z
2021-08-06 13:25 ` [PR PATCH] [Updated] " ram02z
2021-08-06 13:54 ` ram02z
2021-08-06 15:02 ` ram02z
2021-08-06 16:15 ` [PR REVIEW] " paper42
2021-08-06 16:15 ` paper42
2021-08-06 16:36 ` [PR PATCH] [Updated] " ram02z
2021-08-06 16:40 ` ram02z
2021-08-06 16:52 ` ram02z
2021-08-06 21:28 ` ram02z
2021-08-10 14:13 ` [PR PATCH] [Updated] " ram02z
2021-08-10 23:28 ` ram02z
2021-08-10 23:34 ` New packages: rbw-1.3.0, rofi-rbw-0.4.1 ram02z
2021-08-10 23:37 ` [PR PATCH] [Updated] " ram02z
2021-09-13 23:47 ` ram02z
2021-09-13 23:48 ` ram02z
2021-10-12 7:02 ` ram02z
2021-10-12 10:07 ` ram02z
2021-10-31 14:17 ` [PR PATCH] [Updated] " ram02z
2021-10-31 14:36 ` [PR PATCH] [Updated] New packages: rbw-1.4.1, rofi-rbw-0.4.1 ram02z
2021-12-30 21:27 ` ram02z
2022-01-14 16:21 ` [PR PATCH] [Updated] New packages: rbw-1.4.1, rofi-rbw-0.5.0 ram02z
2022-01-18 21:22 ` ram02z
2022-02-19 12:09 ` ram02z
2022-02-25 0:47 ` New packages: rbw-1.4.3, rofi-rbw-0.5.0 TinfoilSubmarine
2022-04-21 17:37 ` [PR REVIEW] " classabbyamp
2022-04-21 17:59 ` ram02z
2022-04-21 20:46 ` Piraty
2022-06-11 15:14 ` [PR PATCH] [Updated] " ram02z
2022-06-11 15:24 ` ram02z
2022-06-18 10:45 ` [PR PATCH] [Updated] " ram02z
2022-06-18 10:48 ` New packages: rbw-1.4.3, rofi-rbw-1.0.0 ram02z
2022-06-18 19:01 ` classabbyamp
2022-06-19 0:19 ` classabbyamp
2022-06-19 18:31 ` [PR PATCH] [Updated] " ram02z
2022-06-19 18:32 ` ram02z
2022-06-20 18:24 ` classabbyamp [this message]
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=20220620182440.VoCLSopuW4oo5rU0pJa8FbpawGlY0PfHrK5WWQhX1MU@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).