From: saltnpepper97 <saltnpepper97@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New Package: compfy
Date: Tue, 28 Nov 2023 18:43:52 +0100 [thread overview]
Message-ID: <20231128174352.n8O_vwF-FJ8Bi8j-sA_kTcljPEa-_R9By_p_y3VE0AU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47464@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 512 bytes --]
New comment by saltnpepper97 on void-packages repository
https://github.com/void-linux/void-packages/pull/47464#issuecomment-1830374124
Comment:
I apologize for the adding and removing this commit yesterday. I realize now that it was a bad idea. Here is my final upload of compfy as a new package for void linux. I think it would be a great addition to the package list as it is essentially Picom but more actively maintained by allusive-dev and has animations included as well as several fixes to base picom.
next prev parent reply other threads:[~2023-11-28 17:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 17:42 [PR PATCH] " saltnpepper97
2023-11-28 17:43 ` saltnpepper97 [this message]
2023-11-28 17:44 ` [PR REVIEW] " abenson
2023-11-28 17:45 ` [PR PATCH] [Closed]: " abenson
2023-11-28 17:46 ` abenson
2023-11-28 17:46 ` abenson
2023-11-28 17:54 ` [PR PATCH] [Updated] " saltnpepper97
2023-11-28 17:55 ` saltnpepper97
2023-11-28 18:07 ` [PR PATCH] [Updated] " saltnpepper97
2023-11-28 18:07 ` saltnpepper97
2023-11-28 18:11 ` [PR REVIEW] " abenson
2023-11-28 18:12 ` abenson
2023-11-28 19:11 ` [PR PATCH] [Updated] " saltnpepper97
2023-11-28 19:13 ` saltnpepper97
2023-11-28 19:14 ` [PR REVIEW] " saltnpepper97
2023-11-28 19:14 ` saltnpepper97
2023-11-28 19:49 ` [PR PATCH] [Updated] " saltnpepper97
2023-11-28 19:50 ` [PR REVIEW] " saltnpepper97
2024-02-04 21:47 ` [PR PATCH] [Closed]: New Package: compfy-1.7.1 saltnpepper97
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=20231128174352.n8O_vwF-FJ8Bi8j-sA_kTcljPEa-_R9By_p_y3VE0AU@z \
--to=saltnpepper97@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).