From: Taylor Blau <me@ttaylorr.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: git@vger.kernel.org
Subject: Re: why does git-send-email unwrap headers?
Date: Wed, 2 Jun 2021 12:53:39 -0400 [thread overview]
Message-ID: <YLe3k1CYMhv9LEeh@nand.local> (raw)
In-Reply-To: <20210602153441.cjmey63x2vudlnk6@nitro.local>
On Wed, Jun 02, 2021 at 11:34:41AM -0400, Konstantin Ryabitsev wrote:
> While it's not *wrong* (the 78-character limit is from a very old RFC), I'm
> curious if this is intentional or just an oversight.
My guess is that this dates back to 5012699d98 (send-email: handle
multiple Cc addresses when reading mbox message, 2009-02-14), which
unfolds all multi-line headers, probably so that parsing the header can
be done line-wise without having to keep track of whether you are
parsing a continuation line or not.
Perl's Mail::Header [1] looks to have support for folding a header
across multiple lines, but I'd just as soon defer to the Perl experts
around here for help using it :).
Thanks,
Taylor
[1]: https://metacpan.org/pod/Mail::Header
next prev parent reply other threads:[~2021-06-02 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 15:34 why does git-send-email unwrap headers? Konstantin Ryabitsev
2021-06-02 16:53 ` Taylor Blau [this message]
2021-06-02 18:04 ` Konstantin Ryabitsev
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=YLe3k1CYMhv9LEeh@nand.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=konstantin@linuxfoundation.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).