From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00, T_SCC_BODY_TEXT_LINE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 133441F852; Sun, 13 Feb 2022 10:22:12 +0000 (UTC) Date: Sun, 13 Feb 2022 10:22:11 +0000 From: Eric Wong To: meta@public-inbox.org Subject: Re: git SHA-256, perl 5.12, FUSE... Message-ID: <20220213102211.GA8960@dcvr> References: <20211105211317.GA12959@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20211105211317.GA12959@dcvr> List-Id: Eric Wong 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/