From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: Re: git SHA-256, perl 5.12, FUSE...
Date: Sun, 13 Feb 2022 10:22:11 +0000 [thread overview]
Message-ID: <20220213102211.GA8960@dcvr> (raw)
In-Reply-To: <20211105211317.GA12959@dcvr>
Eric Wong <e@80x24.org> wrote:
> All of these will probably be in the future of public-inbox;
> but I think I'm going to goof off with these in a
> yet-to-be-announced AGPL project, first...
That project remains unannounced and stalled. My mind isn't
working well enough to implement some of the logic necessary...
But most of the low-level bits are done.
* While working on that project; I've noted git SHA-256 and SHA-1
don't mix for alternates, currently. Neither -extindex, lei nor
v2 inboxes can support a mix of SHA-1 and SHA-256 epochs/alternates.
* Interfacing with FUSE3 is *easy* (at least for users with gcc +
libfuse3-dev + URCU installed). The low-level FUSE API makes
far more sense to me than the high-level FUSE API used by most
language bindings. I'm using a standalone C shim (not Inline::C)
using the FUSE MT-loop to interface with multiple Perl processes
via SOCK_SEQPACKET.
* Perl 5.12 isn't happening:
https://public-inbox.org/meta/20211108183859.GA25072@dcvr/
https://public-inbox.org/meta/20220213101802.GA18993@dcvr/
prev parent reply other threads:[~2022-02-13 10:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 21:13 git SHA-256, perl 5.12, FUSE Eric Wong
2022-02-13 10:22 ` Eric Wong [this message]
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220213102211.GA8960@dcvr \
--to=e@80x24.org \
--cc=meta@public-inbox.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 read-only IMAP folder(s) and NNTP newsgroup(s).