From: Sarir Khamsi <sarir.khamsi@raytheon.com>
Subject: Re: wrong number of mail in my mbox
Date: Wed, 02 Mar 2005 13:00:14 -0700 [thread overview]
Message-ID: <uis49ddip.fsf@raytheon.com> (raw)
In-Reply-To: <87u0nuwydp.fsf@flibuste.net>
sebastien_AEFFACER_@flibuste.net.invalid ( Sébastien Mengin) writes:
> What's wrong with the solution provided in the faq?
> It worked all right at my site...
That is what I am referring to. I have a mail group whose subject
lines do not match up the message bodies. This FAQ item seems like it
might help (if I take every message in that messed up group, move it
to a tmp group, then move it back).
Is there an alternative command that would force Gnus to "recalculate"
message numbers? I looked at nnml-generate-nov-databases but that
didn't help.
Sarir
prev parent reply other threads:[~2005-03-02 20:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-25 13:46 Sébastien Mengin
2005-02-25 16:12 ` Marcus Frings
2005-02-25 19:07 ` Sébastien Mengin
2005-03-02 0:55 ` Sarir Khamsi
2005-03-02 2:54 ` Sébastien Mengin
2005-03-02 20:00 ` Sarir Khamsi [this message]
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=uis49ddip.fsf@raytheon.com \
--to=sarir.khamsi@raytheon.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).