From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: [Patch] define-composed-chars mistake, additions
Date: Fri, 09 Jan 2009 09:39:34 -0800 [thread overview]
Message-ID: <090109093934.ZM1679@torch.brasslantern.com> (raw)
In-Reply-To: <2d460de70901090830s77bbb789p6190a0f2822544ed@mail.gmail.com>
On Jan 9, 5:30pm, Richard Hartmann wrote:
}
} Inline stuff can be affected by line breaks and other crap, though.
If that hasn't been a problem for the previous more than ten years,
why it is going to suddenly become a problem now?
I suppose the answer is "web-based mail clients." Grumble.
} If you want, I can start sending my patches both inline & attached,
} though.
Please don't do that; it both exposes the MIME structure in the mailing
list archive *and* duplicates the information.
If you simply must use attachments, just label them text/plain, unless
they're so huge you've compressed them or some such, of course.
next prev parent reply other threads:[~2009-01-09 17:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 7:14 Benjamin R. Haskell
2009-01-09 9:18 ` Richard Hartmann
2009-01-09 16:01 ` Bart Schaefer
2009-01-09 16:30 ` Richard Hartmann
2009-01-09 17:39 ` Bart Schaefer [this message]
2009-01-09 23:17 ` Richard Hartmann
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=090109093934.ZM1679@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@sunsite.dk \
/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).