From: kaih@khms.westfalen.de (Kai Henningsen)
To: linux-kernel@vger.kernel.org
Subject: Re: Why not "attach" patches?
Date: 24 Jan 2002 08:59:00 +0200 [thread overview]
Message-ID: <8HSVvR$1w-B@khms.westfalen.de> (raw)
In-Reply-To: <a2kac1$m0a$1@cesium.transmeta.com>
In-Reply-To: <a2kac1$m0a$1@cesium.transmeta.com>
hpa@zytor.com (H. Peter Anvin) wrote on 22.01.02 in <a2kac1$m0a$1@cesium.transmeta.com>:
> The common ground most people seems to be able to accept is:
>
> a. Go ahead and make patches as attachments, if your MUA makes it easier;
> b. Be bloody certain they're text/plain attachments.
... and that they have Content-Transfer-Encoding: 7bit or 8bit.
*Not* quoted-printable or base64.
Which means that you lose if the patch contains chars whose 8th bit is
set, if any MTA between you and Linus/Alan/etc. doesn't like that. Which
is not quite unlikely. (But most MUAs won't allow you to send something
like that anyway.)
MfG Kai
next prev parent reply other threads:[~2002-01-24 8:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 17:44 Why not "attach" patches? Martin Eriksson
2002-01-15 17:47 ` David S. Miller
2002-01-15 17:52 ` Martin Dalecki
2002-01-15 18:04 ` Linus Torvalds
2002-01-15 18:50 ` Richard Gooch
2002-01-15 19:28 ` Alan Cox
2002-01-15 19:29 ` Davide Libenzi
2002-01-15 19:49 ` Nicolas Pitre
2002-01-15 22:09 ` Patrick Mochel
2002-01-15 22:16 ` Andreas Dilger
2002-01-16 0:11 ` Removing the whitespaces??? [Was: Re: Why not "attach" patches?] Henning P. Schmiedehausen
2002-01-16 4:16 ` Andreas Dilger
2002-01-17 8:56 ` Ravindra Jaju
2002-01-16 0:26 ` Stuart Young
2002-01-15 23:13 ` Why not "attach" patches? Urban Widmark
2002-01-15 23:51 ` Sebastian Benoit
2002-01-15 19:59 ` Jeff Garzik
2002-01-21 16:15 ` Daniel Phillips
2002-01-22 18:17 ` H. Peter Anvin
2002-01-24 6:59 ` Kai Henningsen [this message]
2002-01-16 11:46 ` Christoph Rohland
2002-01-16 17:22 ` Linus Torvalds
2002-01-15 17:57 ` Kent Borg
2002-01-15 19:38 ` Martin Eriksson
2002-01-15 19:48 ` Anton Altaparmakov
2002-01-15 23:34 ` Johan Kullstam
2002-01-15 18:02 ` Linus Torvalds
2002-01-15 18:39 ` Andi Kleen
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='8HSVvR$1w-B@khms.westfalen.de' \
--to=kaih@khms.westfalen.de \
--cc=linux-kernel@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox