From: inalone <inalone@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: rofi-wayland-1.7.5+wayland1
Date: Tue, 23 May 2023 22:29:04 +0200 [thread overview]
Message-ID: <20230523202904.N07OhiyUSJ9xyQQ3rfAbHtVsOrNYkSW6GxEsxfEWQJM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44054@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 746 bytes --]
New comment by inalone on void-packages repository
https://github.com/void-linux/void-packages/pull/44054#issuecomment-1560079678
Comment:
I've read over instances before in which this package was denied due to either
a) the PR being stale
b) maintainers being unconvinced of its usefulness
As a user of both wofi and rofi, rofi's ecosystem is fantastic. I can easily just search up Rofi scripts, some of which really old, some of which well-established, some of which packaged right here on Void! Using the Wayland friendly rofi "replacements" is not the same experience, even though those projects are great. Rofi is just such a well established project and ecosystem and I think having the lbonn Wayland fork of Rofi is well worthwhile
next prev parent reply other threads:[~2023-05-23 20:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 20:25 [PR PATCH] " inalone
2023-05-23 20:27 ` classabbyamp
2023-05-23 20:27 ` inalone
2023-05-23 20:27 ` inalone
2023-05-23 20:28 ` [PR PATCH] [Updated] " inalone
2023-05-23 20:29 ` inalone [this message]
2023-05-23 20:32 ` [PR REVIEW] " classabbyamp
2023-05-23 20:32 ` classabbyamp
2023-05-23 20:32 ` classabbyamp
2023-05-23 20:38 ` [PR PATCH] [Updated] " inalone
2023-05-23 20:40 ` inalone
2023-08-22 1:44 ` github-actions
2023-08-25 22:35 ` [PR PATCH] [Updated] " inalone
2023-08-27 10:35 ` inalone
2023-09-10 21:59 ` inalone
2023-09-13 19:17 ` inalone
2023-09-24 21:58 ` inalone
2023-12-24 1:47 ` github-actions
2024-01-07 1:49 ` [PR PATCH] [Closed]: " github-actions
-- strict thread matches above, loose matches on Subject: below --
2023-02-03 20:36 [PR PATCH] " subnut
2023-02-03 20:49 ` subnut
2023-02-03 21:14 ` kruceter
2023-02-03 21:17 ` classabbyamp
2023-02-03 22:32 ` subnut
2023-02-03 22:38 ` subnut
2023-05-08 1:53 ` github-actions
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=20230523202904.N07OhiyUSJ9xyQQ3rfAbHtVsOrNYkSW6GxEsxfEWQJM@z \
--to=inalone@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).