From: ori@eigenstate.org
To: theinicke@bss-wf.de, 9front@9front.org
Subject: Re: [9front] [Bug] [PATCH] Mail cannot cope with multi-line header fields
Date: Thu, 10 Sep 2020 14:12:22 -0700 [thread overview]
Message-ID: <F4C02EB6DC83C56813C8B0C8CB2F4793@eigenstate.org> (raw)
In-Reply-To: <1E9189D603E4A86EC6969A0C7524340A@bss-wf.de>
> Maybe we should just get rid of the line breaks altogether (either at info file generation or possibly even before), because this would probably honor the following part of rfc2822 (this is identical in the newest rfc5322):
>
>> Each header field should be treated in its unfolded form for further syntactic and semantic evaluation.
>
> --
> Tobias Heinicke
In that case, yes. If the newlines are not intended to be semantically meaningful,
let's strip them. It simplifies consumers.
next prev parent reply other threads:[~2020-09-10 21:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 19:33 theinicke
2020-09-09 19:50 ` [9front] " ori
2020-09-10 6:27 ` theinicke
2020-09-10 19:58 ` theinicke
2020-09-10 21:12 ` ori [this message]
2020-09-11 21:08 ` theinicke
2020-09-12 21:19 ` theinicke
2020-09-12 22:58 ` ori
2020-09-14 21:49 ` theinicke
2020-09-17 23:01 ` ori
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=F4C02EB6DC83C56813C8B0C8CB2F4793@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
--cc=theinicke@bss-wf.de \
/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).