From: Rupa Schomaker <rupa-list+gnus@rupa.com>
Subject: Re: CVS update of gnus/lisp (nnslashdot.el)
Date: Wed, 22 Aug 2001 09:38:40 -0700 [thread overview]
Message-ID: <m3itfgcanj.fsf@shakti.rupa.com> (raw)
In-Reply-To: <m3r8u59i82.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Wed, 22 Aug 2001 00:11:09 +0200")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Rupa Schomaker <rupa-list+gnus@rupa.com> writes:
>
>> I just updated to the latest. Almost seems to work. If I try to read
>> the "head" article in a slashdot summary I get the warning that
>> slashdot has changed and to update.
>
> Hm... ShengHuo's nnslashdot fixes seem to work OK for me -- I can
> read both the article and the comments in each group.
And today it is working fine. I'll chalk it up to slashdot being
inconsistent. Thanks.
--
-rupa
prev parent reply other threads:[~2001-08-22 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200108210048.CAA30516@quimby.gnus.org>
2001-08-21 20:47 ` Rupa Schomaker
2001-08-21 22:11 ` Lars Magne Ingebrigtsen
2001-08-22 16:38 ` Rupa Schomaker [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=m3itfgcanj.fsf@shakti.rupa.com \
--to=rupa-list+gnus@rupa.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).