From: michael-db <michael-db@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: Trinity Desktop Environment
Date: Mon, 03 Jun 2024 15:13:56 +0200 [thread overview]
Message-ID: <20240603131356.DB12828E59@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19243@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 590 bytes --]
New comment by michael-db on void-packages repository
https://github.com/void-linux/void-packages/issues/19243#issuecomment-2145174513
Comment:
Unless you think it's worth packaging for your own benefit, I wouldn't go just by my comment, Kacper, especially if you don't think it will be accepted as an official package. No one else has commented on this issue this year and I'm used to being in a minority.
(And I'm not entitled to ask others for things like this: I do have several open source contributions "planned" but they seem to get indefinitely displaced by other priorities.)
next prev parent reply other threads:[~2024-06-03 13:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 23:33 [ISSUE] " kpvsky
2020-02-21 21:08 ` Chocimier
2020-02-22 15:36 ` kpvsky
2020-02-22 15:49 ` xtraeme
2020-02-22 15:49 ` xtraeme
2020-03-01 22:22 ` BenEvolent333
2020-03-05 15:58 ` kpvsky
2020-04-14 10:20 ` ScrelliCopter
2020-04-24 17:44 ` ScrelliCopter
2020-04-25 9:10 ` ScrelliCopter
2020-08-18 9:46 ` kpvsky
2020-11-10 8:36 ` ScrelliCopter
2021-12-30 9:43 ` nipos
2022-03-02 16:54 ` Vistaus
2022-04-10 21:41 ` kasesag
2022-08-20 5:12 ` [ISSUE] [CLOSED] " kasesag
2023-05-08 20:06 ` thenktor
2024-05-24 10:24 ` michael-db
2024-06-02 13:58 ` kasesag
2024-06-03 11:25 ` kasesag
2024-06-03 13:13 ` michael-db [this message]
2024-06-03 13:27 ` kasesag
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=20240603131356.DB12828E59@inbox.vuxu.org \
--to=michael-db@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).