unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Kyle Meyer <kyle@kyleam.com>, meta@public-inbox.org
Subject: Re: MH & thread support
Date: Tue, 1 Feb 2022 09:51:39 +0000	[thread overview]
Message-ID: <20220201095139.GA7613@dcvr> (raw)
In-Reply-To: <877dbc5nnq.fsf@kyleam.com>

Kyle Meyer <kyle@kyleam.com> 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.

      parent reply	other threads:[~2022-02-01  9:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-06 18:10 MH & thread support Jakub Kicinski
2022-01-07  1:40 ` Kyle Meyer
2022-01-07  2:22   ` Jakub Kicinski
2022-02-01  9:51   ` 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=20220201095139.GA7613@dcvr \
    --to=e@80x24.org \
    --cc=kuba@kernel.org \
    --cc=kyle@kyleam.com \
    --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).