From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-users@zsh.org
Subject: patches format Re: fndir introspection, site-packages documentation
Date: Mon, 16 Mar 2015 09:36:24 +0000 [thread overview]
Message-ID: <20150316093623.GG1875@tarsus.local2> (raw)
In-Reply-To: <150315121447.ZM27996@torch.brasslantern.com>
Bart Schaefer wrote on Sun, Mar 15, 2015 at 12:14:47 -0700:
> Aside: I don't suppose there's any point in again begging people to stop
> attaching patches as "text/x-patch" or "text/x-diff" or other silly MIME
> types that half my email clients say there is no app for, and the other
> half pass to some miscelleneous (wrong) app because of the ".patch" file
> extension, which someone seems to think has something to do with setting
> up network tunnels.
>
> Grumble. Text bleeping plain, or just put them in the message body.
>
I wouldn't advise people to put patches in the body, since most mail
clients auto-wrap and strip leading/trailing whtiespace by default
(which corrupts empty context lines). Instead, I usually advise people
to attach patches as a file named *.txt. That filename pattern usually
results in text/plain attachments.
> I suppose I should also rant about email client authors who don't have
> a "text/*" fallback. Rant rant. We now return you to your regularly
> scheduled curmudgeonry.
next prev parent reply other threads:[~2015-03-16 9:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 22:41 Roman Neuhauser
2015-03-14 3:39 ` Bart Schaefer
2015-03-15 2:14 ` Roman Neuhauser
2015-03-15 19:14 ` Bart Schaefer
2015-03-16 9:36 ` Daniel Shahaf [this message]
2015-03-16 10:01 ` patches format " Peter Stephenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150316093623.GG1875@tarsus.local2 \
--to=d.s@daniel.shahaf.name \
--cc=schaefer@brasslantern.com \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).