From: Wang Kang <firstname.lastname@example.org>
To: Konstantin Ryabitsev <email@example.com>
Cc: Eric Wong <firstname.lastname@example.org>,
Subject: Re: [PATCH] nntp: header responses use CRLF consistently
Date: Sat, 19 Jan 2019 09:14:15 +0800 (HKT) [thread overview]
Message-ID: <alpine.DEB.email@example.com> (raw)
The problem still exists. (Maybe a Perl 'restart' needed?)
You can test it with:
alpine -url news://nntp.lore.kernel.org/org.kernel.vger.linux-btrfs
The already fixed one:
alpine -url news://news.public-inbox.org/inbox.comp.mail.public-inbox.meta
Remember to press enter on one of the message to see the content, that's
when it will stall.
On Fri, 18 Jan 2019, Konstantin Ryabitsev wrote:
> On Wed, Jan 16, 2019 at 04:58:02AM +0000, Eric Wong wrote:
> > Thanks, I'm pretty sure the following will fix it.
> > Not sure why others hadn't noticed since there's a lot of Alpine
> > users judging from Message-IDs. Anyways I managed to replicate it
> > quickly with alpine in Debian ("alpine -url news://...") and
> > strace quickly showed me the difference.
> > Deploying to news.public-inbox.org shortly.
> > Cc-ing Konstantin for kernel.org.
> The latest master now runs on lore.kernel.org, so this problem should be
> fixed there as well.
next prev parent reply other threads:[~2019-01-19 1:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 2:54 NNTP served by public-inbox stalled in Alpine 2.21.99 Wang Kang
2019-01-16 4:58 ` [PATCH] nntp: header responses use CRLF consistently Eric Wong
2019-01-18 21:04 ` Konstantin Ryabitsev
2019-01-19 1:14 ` Wang Kang [this message]
2019-01-19 4:41 ` Konstantin Ryabitsev
2019-01-19 4:47 ` Wang Kang
2019-01-16 5:25 ` [Alpine-info] NNTP served by public-inbox stalled in Alpine 2.21.99 Wang Kang
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:
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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 read-only IMAP folder(s) and NNTP newsgroup(s).