From: merlyn@stonehenge.com (Randal L. Schwartz)
Subject: has "incorporating new mail" bug been fixed yet?
Date: 23 Dec 1999 09:51:59 -0800 [thread overview]
Message-ID: <m1ln6lczpc.fsf@halfdome.holdit.com> (raw)
So where are we at? Did the latest release fix it so that I can:
M-g on a single nnml group
2 M-g to get all nnml groups at level 2-1
gnus-no-server to start at my level 2-1 groups
without the annoying dozens of "no mail" messages?
(I know, Randal, try it, and let us know...)
Well, just wanted to save the upgrade time if that's still known
broken. :)
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
next reply other threads:[~1999-12-23 17:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-23 17:51 Randal L. Schwartz [this message]
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
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=m1ln6lczpc.fsf@halfdome.holdit.com \
--to=merlyn@stonehenge.com \
/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).