user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: Wang Kang <i@scateu.me>,
	meta@public-inbox.org, alpine-info@u.washington.edu
Subject: Re: [PATCH] nntp: header responses use CRLF consistently
Date: Fri, 18 Jan 2019 16:04:08 -0500	[thread overview]
Message-ID: <20190118210408.GB6330@pure.paranoia.local> (raw)
In-Reply-To: <20190116045802.ikm67b4cwigso3tc@dcvr>

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.

Best,
-K

  reply	other threads:[~2019-01-18 21:04 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 [this message]
2019-01-19  1:14     ` Wang Kang
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

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

  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 \
    --in-reply-to=20190118210408.GB6330@pure.paranoia.local \
    --to=konstantin@linuxfoundation.org \
    --cc=alpine-info@u.washington.edu \
    --cc=e@80x24.org \
    --cc=i@scateu.me \
    --cc=meta@public-inbox.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

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).