From: David Hanak <dhanakDONT@isisSEND.vanderbiltME.eduSPAM>
Subject: Re: Incorrect article count
Date: Mon, 08 Mar 2004 13:04:08 -0600 [thread overview]
Message-ID: <uptbn6tzr.fsf@isisSEND.vanderbiltME.eduSPAM> (raw)
In-Reply-To: <ubrn75h14.fsf@swbell.net>
On Mon, 08 Mar 2004, Peter Lee wrote:
> Thanks for the replies. With the .overview hint, I was able to
> remove the "ghost" articles that appeared in the summary but were not
> on disk. After I did that marking all messages and moving to the
> same folder fixed the numbering problem as it used to.
When ghost articles appear in the overview, you should be able to fix that
by calling nnml-generate-nov-databases.
--
David Hanak - Research Engineer
Institute for Software Integrated Systems | http://www.isis.vanderbilt.edu
Vanderbilt University | Work phone: (615) 343 1319
Box 1829, Station B, Nashville, TN 37235 | PGP key ID: 266BC45F
next prev parent reply other threads:[~2004-03-08 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 16:11 Peter Lee
[not found] ` <ubrn75h14.fsf@swbell.net>
2004-03-08 19:04 ` David Hanak [this message]
[not found] ` <m3k71vl0su.fsf@fed1.frank-schmitt.net>
[not found] ` <wn5smghncle.fsf@linhd-2.ca.nortel.com>
2004-03-09 19:36 ` Frank Schmitt
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=uptbn6tzr.fsf@isisSEND.vanderbiltME.eduSPAM \
--to=dhanakdont@isissend.vanderbiltme.eduspam \
/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).