From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Async NNTP code disabled for now
Date: Mon, 14 Feb 2011 14:12:50 -0800 [thread overview]
Message-ID: <87pqqutgd9.fsf@gnus.org> (raw)
In-Reply-To: <m3pqqu47g4.fsf@jhcloos.com>
James Cloos <cloos@jhcloos.com> writes:
> The bug seems to be that with the async code gnus cannot deal with the
> other side of an nntp session closing the socket. At least not while
> gnus is still on its first iteration through its list of servers.
Right. That sounds likely.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2011-02-14 22:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 18:06 Lars Ingebrigtsen
2011-02-14 21:44 ` James Cloos
2011-02-14 22:12 ` Lars Ingebrigtsen [this message]
2011-02-15 18:16 ` James Cloos
2011-02-18 23:21 ` Lars Ingebrigtsen
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=87pqqutgd9.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=ding@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).