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

Re: How do I make git-format-patch reject 8-bit encodings?

From
TTTabi Timur-B04825 <b04825@freescale.com>
Date
Feb 22, 2011, 00:27 UTC
Message-ID
<4D6302E6.1070602@freescale.com>
In-Reply-To
<7vbp24hqez.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
Show 6 quoted lines
> Feels like an X-Y problem, but wouldn't it be an option to let
> format-patch write into individual files, check these files and reject
> ones that are not 8-bit clean, and then send the result out via
> send-email?  You should be proofreading the format-patch output to catch
> and fix typos before hading them to send-email anyway, so the above would
> be the natural thing to do.
The problem is that it appears that git-send-email is taking normal-looking patches and encoding them as base64, and I don't know about it until after the email is sent.  It also appears to be inconsistent.  I've seen some utf-8 patches emailed as normal text, and other patches emailed as base64.
I don't have any real problem with utf-8, but I want to prevent git-send-email from doing base64 encodings on its own.
-- 
Timur Tabi
Linux kernel developer
Previous: Junio C HamanoNext: Jeff King
Message 3 of 5 in “How do I make git-format-patch reject 8-bit encodings?”
  1. Timur TabiFeb 21, 2011
  2. Junio C HamanoFeb 22, 2011
  3. Tabi Timur-B04825Feb 22, 2011
  4. Jeff KingFeb 22, 2011
  5. Timur TabiFeb 22, 2011

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.