From: paoloschi <paoloschi@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Package request: ffs
Date: Wed, 25 Jan 2023 11:42:43 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41862@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 682 bytes --]
New issue by paoloschi on void-packages repository
https://github.com/void-linux/void-packages/issues/41862
Description:
### Package name
ffs
### Package homepage
https://mgree.github.io/ffs (releases: https://github.com/mgree/ffs/releases)
### Description
The **f**ile **f**ile**s**ystem: mount semi-structured data (like JSON) as a Unix filesystem
Lets you mount semi-structured data as a filesystem, letting you work with modern formats using your familiar shell tools. Currently, _ffs_ supports _JSON_, _YAML_ and _TOML_ with more to come.
### Does the requested package meet the package requirements?
System, Compiled
### Is the requested package released?
Yes
reply other threads:[~2023-01-25 10:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41862@inbox.vuxu.org \
--to=paoloschi@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).