From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-4.2 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF, T_SCC_BODY_TEXT_LINE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 571941F4BE for ; Tue, 30 Jan 2024 06:31:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=80x24.org; s=selector1; t=1706596271; bh=EJ//2WXsSDlUk4b0yMAROJntfSteO+2wmrx9dv6K2uc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=1NqtOs2WhGThh3Pl8QLOdLgWAyNjpRA7Iwww62ARw5QtnIm9vBweBFNxolZCESNk4 U7uf95UqHwWQQvDSGnH9ntiuf3l+YE1fBRxDtgOTfSh3GMEr8gAAaG3iBkZpQ5FjVA fPOF3kMTeAbF3KoWv7Cb5LQhblfuMGHsdvMvbtdU= From: Eric Wong To: meta@public-inbox.org Subject: [PATCH 2/2] doc/lei-mail-formats: update MH read-only status Date: Tue, 30 Jan 2024 06:31:10 +0000 Message-ID: <20240130063110.1116767-3-e@80x24.org> In-Reply-To: <20240130063110.1116767-1-e@80x24.org> References: <20240130063110.1116767-1-e@80x24.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit List-Id: I'm not looking forward to dealing with synchronization problems if we end up dealing with writes... --- Documentation/lei-mail-formats.pod | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/Documentation/lei-mail-formats.pod b/Documentation/lei-mail-formats.pod index 930c5d76..618bada2 100644 --- a/Documentation/lei-mail-formats.pod +++ b/Documentation/lei-mail-formats.pod @@ -83,9 +83,19 @@ mbox. =head1 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. +Preliminary support for reads as of 2.0.0. Locking semantics differ +incompatibly amongst existing writers: Python and nmh appear +compatible with each other, while mutt appears racy and unsuitable +for parallel access due to rename(2) potentially clobbering the +C<.mh_sequences> file. More info about other clients is greatly +appreciated. + +Sequence numbers may be packed and reused by some writers, so lei +users may need to run L if inotify|kevent +missed packing while L wasn't running. + +lei is safe for reading mlmmj archives as MH since mlmmj neither +packs nor uses a .mh_sequences file to store state. =head1 MMDF