Gnus development mailing list
 help / color / mirror / Atom feed
From: Bud Rogers <budr@sirinet.net>
Subject: Re: has "incorporating new mail" bug been fixed yet?
Date: 23 Dec 1999 14:39:17 -0600	[thread overview]
Message-ID: <87d7rxz91m.fsf@twocups.sirinet.net> (raw)
In-Reply-To: merlyn@stonehenge.com's message of "23 Dec 1999 12:18:00 -0800"

merlyn@stonehenge.com (Randal L. Schwartz) writes:

> Do you have a directory source?  I use procmail-like software to
> presort my mail, so I have (mumble) 50-some .spool files in my
> .incoming directory.  And I see 50-some "new messages" messages each
> time.  It probably would be OK if GNUS deleted the files, but I think
> we'd have a locking staredown problem at that point.

No, I use nnml-split-fancy.  Sorry.

-- 
Bud Rogers <budr@sirinet.net>	http://www.sirinet.net/~budr/zamm.html



  reply	other threads:[~1999-12-23 20:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-23 17:51 Randal L. Schwartz
1999-12-23 18:23 ` David S. Goldberg
1999-12-23 20:16   ` Randal L. Schwartz
1999-12-23 18:39 ` Bud Rogers
1999-12-23 20:18   ` Randal L. Schwartz
1999-12-23 20:39     ` Bud Rogers [this message]
1999-12-23 20:39     ` David S. Goldberg
1999-12-24  6:15       ` Randal L. Schwartz
1999-12-24 23:46       ` Simon Josefsson

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=87d7rxz91m.fsf@twocups.sirinet.net \
    --to=budr@sirinet.net \
    /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).