Re: [PATCH/POLL] git-format-patch: the default suffix is now .patch, not .txt

From: Junio C Hamano <junkio@cox.net>
Date: Jan 18, 2007, 09:10 UTC
Message-ID: <7vps9cn1ip.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <81b0412b0701180018i208e4158k2dd3e9ecdfa79b13@mail.gmail.com>

"Alex Riesen" <raa.lkml@gmail.com> writes:

> On 1/18/07, Shawn O. Pearce <spearce@spearce.org> wrote:

>> Thus the file extension has no impact on how the mail client should
>> treat it.
>
> He will attach it. It's typical for outlook users.

If that is the case, I highly suspect that it is one more reason not to mark the file with .txt; Outlook may say "Hey, it's TEXT, so let's linewrap it, quote-balance it and add all sorts of nice frills to make it easier to read for human consumption".

Assuming that it does not understand what a .patch is, we would have a better chance to force it not to look at nor touch the contents, and not getting our patches corrupted.

$ 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.