From: userabc123xyz <userabc123xyz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: zyn-fusion
Date: Sun, 11 Oct 2020 16:26:14 +0200 [thread overview]
Message-ID: <20201011142614.czYcZlN2ILEXEPALz9gFG3lbRHOJoW61KWPTDbUTQKg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25507@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 317 bytes --]
New comment by userabc123xyz on void-packages repository
https://github.com/void-linux/void-packages/issues/25507#issuecomment-706701815
Comment:
uh, I didn't know that Void's zynaddsubfx version didn't come with zyn-fusion by default
if it indeed doesn't come with zyn-fusion, then I wholly support your request
next prev parent reply other threads:[~2020-10-11 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-11 3:59 [ISSUE] " harrisonthorne
2020-10-11 13:03 ` userabc123xyz
2020-10-11 14:26 ` userabc123xyz [this message]
2021-01-01 18:18 ` russnes
2021-01-01 18:26 ` russnes
2023-07-18 14:31 ` luzpaz
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=20201011142614.czYcZlN2ILEXEPALz9gFG3lbRHOJoW61KWPTDbUTQKg@z \
--to=userabc123xyz@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).