From: era@iki.fi
Subject: Re: Trailing whitespace stripping
Date: 30 Oct 2003 19:08:38 +0200 [thread overview]
Message-ID: <877k2mbqor.fsf@era.iki.fi> (raw)
In-Reply-To: <v9znfizocx.fsf@marauder.physik.uni-ulm.de>
On Thu, 30 Oct 2003 17:23:10 +0100, Reiner Steib
<4.uce.03.r.s@nurfuerspam.de> posted to gmane.emacs.gnus.general:
> I think it should be possible to send both, *inline* patches and
> text/* attachments, without any whitespace stripping, because some
> mailing lists (or list software) doesn't allow attachments at all.
Isn't one of the purposes of Quoted-Printable encoding is to allow for
an unambiguous and transport-safe way to preserve trailing spaces?
Merely making sure you don't strip them when you send them is hardly
sufficient (as in, adequately robust) in any event.
/* era */
--
The email address era the contact information Just for kicks, imagine
at iki dot fi is heavily link on my home page at what it's like to get
spam filtered. If you <http://www.iki.fi/era/> 500 pieces of spam for
want to reach me, see instead. each wanted message.
prev parent reply other threads:[~2003-10-30 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 16:23 Reiner Steib
2003-10-30 17:08 ` era [this message]
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=877k2mbqor.fsf@era.iki.fi \
--to=era@iki.fi \
/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.
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).