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 5523B1F852; Tue, 1 Feb 2022 09:51:39 +0000 (UTC) Date: Tue, 1 Feb 2022 09:51:39 +0000 From: Eric Wong To: Jakub Kicinski Cc: Kyle Meyer , meta@public-inbox.org Subject: Re: MH & thread support Message-ID: <20220201095139.GA7613@dcvr> References: <20220106101020.09638bd8@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> <877dbc5nnq.fsf@kyleam.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <877dbc5nnq.fsf@kyleam.com> List-Id: Kyle Meyer wrote: > Jakub Kicinski writes: > > - how do the plans for MH email format support look? It'd be great to > > fetch emails with lei directly to claws-mail (which seems to be used > > by a number of kernel devs, at least) > > I don't have any informed opinions on this and don't know what Eric's > thoughts are, but fwiw this is what he wrote in lei-mail-formats(5): > > MH > Not yet supported, locking semantics (or lack thereof) appear to make > it unsuitable for parallel access. It is widely-supported by a variety > of MUAs and mailing list managers, however. Yeah, read-write is tricky since I don't know how parallel writers handle sequence numbers or message flags w/o stepping over each other. Write-to-temp-file-then-rename means one of the renamers loses... Read-only is more likely, maybe... I fear I'm too drain bamaged :< And whatever gets added ends up being support a burden forever.