From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH 2/2] nnmaildir: Use a 'num' file, instead of a directory
Date: Thu, 24 Jun 2010 12:52:25 -0500 [thread overview]
Message-ID: <87bpb0jp2e.fsf@lifelogs.com> (raw)
In-Reply-To: <CAEBD542-B911-462F-8D61-777E22EEFFA1@gmail.com>
On Thu, 27 May 2010 15:09:08 -0600 John Wiegley <jwiegley@gmail.com> wrote:
JW> This patch causes nnmaildir to use a "num" file to track the next
JW> available article number, rather than creating N empty files.
JW> However, this only works for new groups. Existing groups, which use
JW> the directory, will continue to. If you want to switch to using
JW> file-based numbering, you must convert your Maildir using the
JW> attached script (it's also copied to the commit description in the
JW> patch).
IIRC (and Paul Jarc may want to comment) something similar was discussed
in http://thread.gmane.org/gmane.emacs.gnus.general/66245/focus=66247
I'm not sure I want to give up concurrent spool access in nnmaildir so I
left things alone back then. I have recently experienced slow nnmaildir
performance too (see
http://article.gmane.org/gmane.emacs.gnus.general/69723). Maybe we can
make this a backend parameter, off by default, and ask whenever someone
creates a new nnmaildir backend in Gnus? I don't think we need to
support the conversion you described, we should only support it for new
nnmaildirs. What do you think?
Ted
next parent reply other threads:[~2010-06-24 17:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEBD542-B911-462F-8D61-777E22EEFFA1@gmail.com>
2010-06-24 17:52 ` Ted Zlatanov [this message]
[not found] ` <m31vbt4s1c.fsf@multivac.cwru.edu>
2010-08-13 0:15 ` Ted Zlatanov
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=87bpb0jp2e.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.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).