From: prj@po.cwru.edu (Paul Jarc)
Subject: announce: nnmaildir 2001.07.30
Date: Mon, 30 Jul 2001 02:42:03 -0400 [thread overview]
Message-ID: <m3hevuj4tq.fsf@multivac.cwru.edu> (raw)
<URL:http://multivac.cwru.edu./nnmaildir/>
CHANGES:
bufixes:
- narrow to header before nnheader-parse-head
features:
- server parameter get-new-mail allows traditional mail splitting
With mail splitting, I think nnmaildir should now have all the
functionality of nnml, along with some extras. I've been told
nnmaildir feels faster than nnml, at least on ReiserFS. Still,
nnmaildir may not be for everyone. It uses twice as many inodes as
nnml. Half of these are for small files (~200 bytes each), which
aren't handled well by block-structured filesystems.
paul
reply other threads:[~2001-07-30 6:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m3hevuj4tq.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
/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).