git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: why does git-send-email unwrap headers?

From
Taylor Blau <me@ttaylorr.com>
Date
Jun 2, 2021, 16:53 UTC
Message-ID
<YLe3k1CYMhv9LEeh@nand.local>
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
Previous: Konstantin RyabitsevNext: Konstantin Ryabitsev
Message 2 of 3 in “why does git-send-email unwrap headers?”
  1. Konstantin RyabitsevJun 2, 2021
  2. Taylor BlauJun 2, 2021
  3. Konstantin RyabitsevJun 2, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.