From: Slawek Zak <S.Zak@altkom.com>
Subject: Re: Dissappearing messages
Date: 31 Jan 2000 19:12:25 +0100 [thread overview]
Message-ID: <874sbum7p2.fsf@localhost.localnet> (raw)
In-Reply-To: Karl Kleinpaste's message of "31 Jan 2000 10:28:53 -0500"
Karl Kleinpaste <karl@justresearch.com> writes:
> Is the article in question actually missing, or is there some kind of
> bookkeeping error happening in nnml?
After closer investigation (guessing from Date:) they seem to be virtual
zero-line-long copies of articles coming right after them (next in
thread). They are missing in the spool.
Examples of these 'afters' in my ding group are:
Message-ID: <oq66wg6eux.fsf@titan.progiciels-bpi.ca>
Message-ID: <19991229205835.A3914@sre-4-139.urbanet.ch>
Message-ID: <87zoty24oh.fsf@iname.com>
My threading settings :
;; Threading
(setq
gnus-build-sparse-threads 'some
gnus-thread-hide-subtree t
gnus-thread-indent-level 2)
/S
next prev parent reply other threads:[~2000-01-31 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-30 22:30 Slawek Zak
2000-01-31 4:51 ` Karl Kleinpaste
2000-01-31 10:03 ` Slawek Zak
2000-01-31 15:28 ` Karl Kleinpaste
2000-01-31 18:12 ` Slawek Zak [this message]
2000-02-03 19:57 ` Slawek Zak
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=874sbum7p2.fsf@localhost.localnet \
--to=s.zak@altkom.com \
--cc=zaks@prioris.im.pw.edu.pl \
/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).