From: n3v3rde4d <n3v3rde4d@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: Cloakify (Text-based Steganography Tool)
Date: Thu, 22 Dec 2022 21:57:28 +0100 [thread overview]
Message-ID: <20221222205728.ifPB1Lsm5bN-M7vFlCoFW-zz0KYc-o3iZ2JPQo4H0ng@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41219@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 250 bytes --]
New comment by n3v3rde4d on void-packages repository
https://github.com/void-linux/void-packages/issues/41219#issuecomment-1363333333
Comment:
Alright, so would that mean "cloakify" can work on void? Does that mean the request will be approved?
next prev parent reply other threads:[~2022-12-22 20:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 18:46 [ISSUE] " n3v3rde4d
2022-12-22 11:17 ` Eloitor
2022-12-22 17:00 ` n3v3rde4d
2022-12-22 17:31 ` Eloitor
2022-12-22 20:57 ` n3v3rde4d [this message]
2022-12-22 21:20 ` classabbyamp
2023-01-06 16:07 ` Eloitor
2023-01-06 21:45 ` n3v3rde4d
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=20221222205728.ifPB1Lsm5bN-M7vFlCoFW-zz0KYc-o3iZ2JPQo4H0ng@z \
--to=n3v3rde4d@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).