From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] maildir history
Date: Sat, 6 Feb 2021 16:18:22 +0100 [thread overview]
Message-ID: <CAFSF3XMTDxd4HbV-8tdLbk4gkrXQV695pZWt_x3pFEo9Tf63sw@mail.gmail.com> (raw)
In-Reply-To: <E6244635-39C7-4AA1-B871-E06783FAE324@stanleylieber.com>
which part of the mail chapter exactly?
i grepped for maildir also, couldnt find it. neither could i find any
mention of mbox.
On 2/6/21, Stanley Lieber <sl@stanleylieber.com> wrote:
> On February 6, 2021 9:15:26 AM EST, hiro <23hiro@gmail.com> wrote:
>>9front upas is all based on erik's nupas code.
>>
>>afterwards it got modified a lot, so much that it might be a rewrite
>>would have been faster.
>>
>>steve: not sure i get your specific question: are you asking if mdir
>>is better than mbox?
>>if yes, then i would agree that without more tooling around it,
>>without indexes around it, our mdir format is still not a very
>>accessible mail archive, but if you make your own indexes and some
>>tooling i think it's much easier based on mdir than on mbox where you
>>would mostly need to do byte-wise seek offsets as opposed to
>>file-granular read operations when you want to access a mail.
>>
>
> read the mail chapter in UNIX-HATERS, and read about why maildir was
> created. all of these problems are as old as e-mail.
>
> sl
>
next prev parent reply other threads:[~2021-02-06 21:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-06 11:10 Steve Simon
2021-02-06 11:35 ` Kurt H Maier
2021-02-06 14:15 ` hiro
2021-02-06 14:38 ` hiro
2021-02-06 15:06 ` Stanley Lieber
2021-02-06 15:18 ` hiro [this message]
2021-02-06 21:36 ` Kurt H Maier
2021-02-06 22:25 ` Steffen Nurpmeso
2021-02-06 22:46 ` Kurt H Maier
2021-02-07 0:02 ` Steffen Nurpmeso
2021-02-07 0:20 ` Kurt H Maier
2021-02-07 0:21 ` hiro
2021-02-09 10:37 ` Steve Simon
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFSF3XMTDxd4HbV-8tdLbk4gkrXQV695pZWt_x3pFEo9Tf63sw@mail.gmail.com \
--to=23hiro@gmail.com \
--cc=9front@9front.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 NNTP newsgroup(s).