From: Wes Hardaker <wjhardaker@ucdavis.edu>
Cc: Hrvoje Niksic <hniksic@srce.hr>,
bugs@gnus.org (The Gnus Bugfixing Girls + Boys),
ding@gnus.org
Subject: Re: Gnus fails to show some email messages
Date: 26 Mar 1998 09:19:28 -0800 [thread overview]
Message-ID: <sdlntx4bfj.fsf@oakdale.ucdavis.edu> (raw)
In-Reply-To: Wes Hardaker's message of "26 Mar 1998 07:32:37 -0800"
Here's another example, since it just happened to me again, details
below:
I just examined the situation a bit further. The articles are in a
thread where the rest of the articles in the thread are expired. C-u
enter shows the thread in question, where it didn't exist normally.
group buffer:
3 3/ 0: dcas
summary buffer thread in question (C-u enter to see them):
E ++ 644=[ 105: Ken Weiss ] 6 prelim. Kerberos deployment plan
E ++ 644=[ 34: Ken Weiss ] 5
E + 135 [ 22: Chris Lambertus ] 1
EA++ 644=[ 60: Ken Weiss ] 2
++ 632 [ 29: Wes Hardaker ] 1
++ 638 [ 82: Doreen Meyer ] 1
The last two lines are the articles that aren't shown normally...
If I un-expire any one of the parents (the top two lines), the thread
shows up again. If I un-expire the third one (not a parent) it
disappears too.
Lars, it looks like my problem is quite possibly related to
threading... I even removed all of my group parameters on the parent
topic to make sure none of those were affecting things and the bug is
still present.
More details:
("nnml:dcas" 3
((1 . 53)
(55 . 59)
(62 . 62))
((expire 53
(55 . 59)
62)
(reply 59))
(nnml "")
nil)
The summary buffer does not show articles 60 and 61 (it does show 54):
.overview lines:
60 Re: prelim. Kerberos deployment plan Wes Hardaker <wjhardaker@ucdavis.edu> 24 Mar 1998 13:31:13 -0800 <sdsoo7ixni.fsf@oakdale.ucdavis.edu> <v03102839b13db59cf4af@[128.120.226.137]>; from Ken Weiss on Tue, Mar 24, 1998 at 11:10:53AM -0800 <v03102837b13daa7755a9@[128.120.226.137]> <v03102839b13db59cf4af@[128.120.226.137]> <v0310283cb13dbe5f045d@[128.120.226.137]> 811 29 Xref: oakdale.ucdavis.edu dcas:60
61 Re: prelim. Kerberos deployment plan Doreen Meyer <dimeyer@ucdavis.edu> Tue, 24 Mar 1998 13:34:08 -0800 <v03102808b13dd559193a@[128.120.226.189]> <19980324112506.25184@zen.ucdavis.edu> <v03102839b13db59cf4af@[128.120.226.137]>; from Ken Weiss on Tue, Mar 24, 1998 at 11:10:53AM -0800 <v03102837b13daa7755a9@[128.120.226.137]> <v03102839b13db59cf4af@[128.120.226.137]> 3608 82 Xref: oakdale.ucdavis.edu dcas:61
The files exist:
% scan +. 60 61
60 03/24 Wes Hardaker Re: prelim. Kerberos deployment plan<<>>>>> On T
61 03/24 Doreen Meyer Re: prelim. Kerberos deployment plan<<Ken/Chris,
--
"Ninjas aren't dangerous. They're more afraid of you than you are of them."
next prev parent reply other threads:[~1998-03-26 17:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-26 12:53 Hrvoje Niksic
1998-03-26 13:25 ` Stefanie Teufel
1998-03-26 14:57 ` Hrvoje Niksic
1998-03-26 15:24 ` Bruce Stephens
1998-03-26 15:29 ` Hrvoje Niksic
1998-03-26 15:58 ` Bruce Stephens
1998-03-26 15:32 ` Wes Hardaker
1998-03-26 17:05 ` Stefanie Teufel
1998-03-26 17:19 ` Wes Hardaker [this message]
1998-03-26 18:11 ` Stefanie Teufel
1998-03-26 21:24 ` Dan Christensen
1998-03-27 20:59 ` Kim-Minh Kaplan
1998-04-01 0:16 ` Eze Ogwuma
1998-04-01 17:23 ` Kim-Minh Kaplan
1998-04-01 20:44 ` Eze Ogwuma
1998-04-26 12:06 ` Gnus fails to show some email messages (and The horrible bug) Eze Ogwuma
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=sdlntx4bfj.fsf@oakdale.ucdavis.edu \
--to=wjhardaker@ucdavis.edu \
--cc=bugs@gnus.org \
--cc=ding@gnus.org \
--cc=hniksic@srce.hr \
/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).