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

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

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

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:42:49

"Alex Riesen" [off-list ref] writes:
On 1/18/07, Shawn O. Pearce [off-list ref] wrote:
quoted
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.

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

From: Alex Riesen <hidden>
Date: 2016-06-15 22:42:49

On 1/18/07, Junio C Hamano [off-list ref] wrote:
quoted
quoted
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".
No, it wont (and doesn't). It would be "too clever to be useful".
Outlook is too _stupid_ to be useful.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help