From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Pop weirdness in p0.77
Date: 26 Feb 1999 15:44:10 +0100 [thread overview]
Message-ID: <m3k8x5z0lh.fsf@quimbies.gnus.org> (raw)
In-Reply-To: Neil Crellin's message of "26 Feb 1999 00:47:19 -0800"
Neil Crellin <neilc@Tesserae.COM> writes:
> I periodically see a different number of new articles when I enter a
> group than the *Group* summary said were there. One time I took a
> close look at the .overview file and found it'd just skipped one of
> the articles it'd written into the directory, ie articles 1546, 1547,
> 1548 and 1549 existed, with both 1548 and 1549 newly fetched messages,
> but the .overview file had entries for 1546, 1547 and 1549, no 1548.
I'll try to look into it.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1999-02-26 14:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-22 21:39 Matt Pharr
1999-02-22 22:50 ` Jack Vinson
1999-02-24 18:27 ` Aaron M. Ucko
1999-02-24 21:58 ` Brian Gorka
1999-02-25 2:26 ` Neil Crellin
1999-02-26 0:58 ` Neil Crellin
1999-02-24 23:28 ` Shane Holder
1999-02-25 1:30 ` Matt Pharr
1999-02-26 6:30 ` Lars Magne Ingebrigtsen
1999-02-26 8:47 ` Neil Crellin
1999-02-26 14:44 ` Lars Magne Ingebrigtsen [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=m3k8x5z0lh.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
/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).