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

Re: MIME problem when using git format-patch / git am

From
Peter Krefting <peter@softwolves.pp.se>
Date
Apr 26, 2010, 08:50 UTC
Message-ID
<alpine.DEB.2.00.1004260948070.22806@ds9.cixit.se>
In-Reply-To
<20100426014941.GA29220@progeny.tock>
Jonathan Nieder:
> This leads to a question: what if one wants to include a word that quotes 
> to more than 75 characters?

You just split it into two encoded words. The whitespace between the encoded words is there for syntactic reasons only, it is not included in the final result if both parts are encoded words (look at the "Examples" section of the RFC for some examples of how it works).

-- 
\\// Peter - http://www.softwolves.pp.se/
Previous: Jonathan NiederNext: Jonathan Nieder
Message 3 of 4 in “MIME problem when using git format-patch / git am”
  1. Øyvind A. HolmApr 25, 2010
  2. Jonathan NiederApr 26, 2010
  3. Peter KreftingApr 26, 2010
  4. Jonathan NiederApr 27, 2010

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.