From: Russ Allbery <rra@stanford.edu>
Subject: Re: Proposed change of nnmail-remove-list-identifiers
Date: Thu, 20 May 2004 17:37:41 -0700 [thread overview]
Message-ID: <87r7tewr6y.fsf@windlord.stanford.edu> (raw)
In-Reply-To: <m34qqbrqj7.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Thu, 20 May 2004 18:50:52 +0200")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Hm... well, the Gmane mail-to-news scripts are way more resilient than
> the ones on quimby.gnus.org; that's for sure. But I'm not quite sure
> what this is supposed to mean. Perhaps it's that old inn bug where a
> header that looks like
> Something:
> And here's the continuation line
> is interpreted as an empty header?
Yeah, that one may still be around even in the latest versions. I'll try
to take a crack at fixing it.
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
prev parent reply other threads:[~2004-05-21 0:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-25 17:28 Jonas Steverud
2004-05-16 12:25 ` Lars Magne Ingebrigtsen
2004-05-20 1:53 ` Jesper Harder
2004-05-20 2:43 ` Lars Magne Ingebrigtsen
2004-05-20 3:09 ` Jesper Harder
2004-05-20 16:50 ` Lars Magne Ingebrigtsen
2004-05-21 0:37 ` Russ Allbery [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=87r7tewr6y.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).