From: Russ Allbery <rra@stanford.edu>
Subject: Re: Small, but possibly fatal change in nntp.el
Date: 24 Jan 2001 21:02:27 -0800 [thread overview]
Message-ID: <ylzoggjkbg.fsf@windlord.stanford.edu> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "24 Jan 2001 12:30:10 +0100"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> I've just committed a change to nntp.el that makes
> nntp-open-connection notice whether it got a 200 response back or not,
> and if it didn't, it hangs up.
I haven't looked at the change, but I assume you're allowing 201 as well?
Read-only servers are useful.
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
next prev parent reply other threads:[~2001-01-25 5:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-24 11:30 Lars Magne Ingebrigtsen
2001-01-24 22:39 ` Lee Cantey
2001-01-25 0:51 ` ShengHuo ZHU
2001-01-25 1:11 ` Lee Cantey
2001-01-25 5:02 ` Russ Allbery [this message]
2001-01-25 5:11 ` ShengHuo ZHU
2001-01-30 8:36 ` Didier Verna
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=ylzoggjkbg.fsf@windlord.stanford.edu \
--to=rra@stanford.edu \
/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).