From: David C Worenklein <dcw@gcm.com>
Cc: ding@ifi.uio.no
Subject: Re: Articles spuriously marked as read?
Date: Tue, 19 Mar 96 08:47:54 -0500 [thread overview]
Message-ID: <9603191347.AA26049@mis_bo9.it.gcm.com> (raw)
In-Reply-To: larsi@ifi.uio.no's message of 19 Mar 1996 02:24:52 +0100
> From: larsi@ifi.uio.no (Lars Magne Ingebrigtsen)
> Date: 19 Mar 1996 02:24:52 +0100
> Organization: Dept. of Informatics, University of Oslo, Norway
> X-From-Line: ding-request@ifi.uio.no Mon Mar 18 21:10:38 1996
>
> I've lately had a nagging feeling of having articles disappear on me.
> I'll be reading a followup to some article, and find I can't really
> remember reading the original article.
This may be an nntp problem. Sometimes articles aren't properly
propogated -- site x will get an article that you don't. Then user@x
follows-up to the article, and the follow-up hits your site.
next prev parent reply other threads:[~1996-03-19 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-03-19 1:24 Lars Magne Ingebrigtsen
1996-03-19 13:47 ` David C Worenklein [this message]
1996-03-19 20:55 ` Lars Magne Ingebrigtsen
1996-03-19 14:04 ` Jack Vinson
1996-03-19 17:31 ` Per Persson
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=9603191347.AA26049@mis_bo9.it.gcm.com \
--to=dcw@gcm.com \
--cc=ding@ifi.uio.no \
/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).