From: Lee Revell <rlrevell@joe-job.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@osdl.org>
Subject: [PATCH] SubmittingPatches: improve documentation re: buggy mailers
Date: Mon, 26 Dec 2005 13:05:24 -0500 [thread overview]
Message-ID: <1135620324.8293.57.camel@mindpipe> (raw)
There are plenty of perfectly good mailers available that don't mangle
patches. Warn users about buggy mailers in general and Thunderbird in
particular.
Signed-Off-By: Lee Revell <rlrevell@joe-job.com>
--- linux-2.6.15-rc5-rt2/Documentation/SubmittingPatches-orig 2005-12-26 13:01:51.000000000 -0500
+++ linux-2.6.15-rc5-rt2/Documentation/SubmittingPatches 2005-12-26 13:03:27.000000000 -0500
@@ -186,6 +186,10 @@
For this reason, all patches should be submitting e-mail "inline".
WARNING: Be wary of your editor's word-wrap corrupting your patch,
if you choose to cut-n-paste your patch.
+WARNING: Avoid Mozilla's Thunderbird email client, unlike other
+popular mailers it seems to be incapable of sending
+non-whitespace-damaged patches.
+
Do not attach the patch as a MIME attachment, compressed or not.
Many popular e-mail applications will not always transmit a MIME
@@ -193,8 +197,8 @@
code. A MIME attachment also takes Linus a bit more time to process,
decreasing the likelihood of your MIME-attached change being accepted.
-Exception: If your mailer is mangling patches then someone may ask
-you to re-send them using MIME.
+No exceptions. If your mailer is mangling patches then you will be
+told to get a better mailer.
reply other threads:[~2005-12-26 18:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1135620324.8293.57.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=akpm@osdl.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.