git SHA-256, perl 5.12, FUSE...

git SHA-256, perl 5.12, FUSE...

[Eric Wong]

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...

A bit tired after the 1.7 cycle and need a short break that
doesn't involve TCP (yet).  But I've already found+fixed several
things related to public-inbox while half-way working on
aforementioned project:

public-inbox.git
54bc9f163df41423 (git: fix numerous bugs in git_quote and git_unquote, 2021-05-09)

git.git
00bc8390d8cd764c (remote-curl: fix clone on sha256 repos, 2021-05-11)

Re: git SHA-256, perl 5.12, FUSE...

[Eric Wong]

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/