From: hholst80 <hholst80@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: SwayNotificationCenter-0.7.2
Date: Thu, 06 Jul 2023 14:39:33 +0200 [thread overview]
Message-ID: <20230706123933.5knAFbaqfTI4HDU1gxQdxOAX243NfEnQ5o5kkJGyV5A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40099@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 376 bytes --]
New comment by hholst80 on void-packages repository
https://github.com/void-linux/void-packages/pull/40099#issuecomment-1623610249
Comment:
In other distros this package is called "swaync" and given how hard it is to find packages I think it would make sense with at least some kind of virtual link / pkg to associate the name "swaync" with the pkg "SwayNotificatonCenter"?
next prev parent reply other threads:[~2023-07-06 12:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 6:26 [PR PATCH] New package: swaync-0.7.2 akhiljalagam
2022-10-22 6:27 ` akhiljalagam
2022-10-22 6:40 ` [PR REVIEW] " classabbyamp
2022-10-22 6:42 ` akhiljalagam
2022-10-22 6:42 ` classabbyamp
2022-10-22 6:44 ` classabbyamp
2022-10-22 10:35 ` akhiljalagam
2022-10-22 13:08 ` classabbyamp
2022-10-22 20:21 ` cinerea0
2022-10-22 20:55 ` classabbyamp
2022-10-22 21:28 ` cinerea0
2022-10-23 5:21 ` akhiljalagam
2022-10-23 5:23 ` akhiljalagam
2022-10-23 5:26 ` akhiljalagam
2022-10-23 5:32 ` [PR PATCH] [Updated] " akhiljalagam
2022-10-23 5:33 ` [PR REVIEW] " akhiljalagam
2022-10-23 5:33 ` akhiljalagam
2022-10-23 5:34 ` akhiljalagam
2022-10-23 5:37 ` [PR PATCH] [Updated] New package: SwayNotificationCenter-0.7.2 akhiljalagam
2022-11-02 18:55 ` akhiljalagam
2022-12-17 14:34 ` akhiljalagam
2023-01-12 5:46 ` akhiljalagam
2023-04-01 18:52 ` hochata
2023-06-24 13:32 ` [PR PATCH] [Closed]: " Duncaen
2023-07-06 12:39 ` hholst80 [this message]
2023-07-06 15:10 ` akhiljalagam
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=20230706123933.5knAFbaqfTI4HDU1gxQdxOAX243NfEnQ5o5kkJGyV5A@z \
--to=hholst80@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).