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

why does git-send-email unwrap headers?

From
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Date
Jun 2, 2021, 15:34 UTC
Message-ID
<20210602153441.cjmey63x2vudlnk6@nitro.local>
Hello:

I've noticed that when a message is sent with git-send-email, it will unwrap all existing headers into a single line, such that:

    Some-header: This is a long header that happens to be longer than 78
     characters and is therefore wrapped at whitespace chars to properly span
     across multiple lines
becomes:
    Some-header: This is a long header that happens to be longer than 78 characters and is therefore wrapped at whitespace chars to properly span across multiple lines

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.

-K
Next: Taylor Blau
Message 1 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.