All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael-lists@free-electrons.com>
To: rob@landley.net
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] Documentation: mention email-clients.txt in SubmittingPatches
Date: Fri, 18 Jan 2008 11:20:02 +0100	[thread overview]
Message-ID: <200801181120.03168.michael-lists@free-electrons.com> (raw)

Applies to 2.6.24-rc8-git2

I was struggling to get my email-client no to mangle my patch files,
and I didn't find enough information in the SubmittingPatches file.
By looking for more information on the web, I eventually found the
email-clients.txt file, and it answered all my needs

This patch adds a reference to email-clients.txt in SubmittingPatches,
and Mozilla related information which is no longer accurate
(as opposed to the details found in email-clients.txt).

This should be helpful for people sending their first patches,
or not sending patches on a frequent basis.

Michael.

--
Signed-off-by: Michael Opdenacker <michael@free-electrons.com>

diff -Naur linux-2.6.24-rc8-git2/Documentation/SubmittingPatches linux-2.6.24-rc8-git2-sp/Documentation/SubmittingPatches
--- linux-2.6.24-rc8-git2/Documentation/SubmittingPatches	2008-01-17 09:48:56.000000000 +0100
+++ linux-2.6.24-rc8-git2-sp/Documentation/SubmittingPatches	2008-01-18 10:29:46.000000000 +0100
@@ -220,20 +220,8 @@
 Exception:  If your mailer is mangling patches then someone may ask
 you to re-send them using MIME.
 
-
-WARNING: Some mailers like Mozilla send your messages with
----- message header ----
-Content-Type: text/plain; charset=us-ascii; format=flowed
----- message header ----
-The problem is that "format=flowed" makes some of the mailers
-on receiving side to replace TABs with spaces and do similar
-changes. Thus the patches from you can look corrupted.
-
-To fix this just make your mozilla defaults/pref/mailnews.js file to look like:
-pref("mailnews.send_plaintext_flowed", false); // RFC 2646=======
-pref("mailnews.display.disable_format_flowed_support", true);
-
-
+See Documentation/email-clients.txt for hints about configuring
+your e-mail client so that it sends your patches untouched.
 
 8) E-mail size.
 

-- 
Michael Opdenacker, Free Electrons
Free Embedded Linux Training Materials
on http://free-electrons.com/training
(More than 1500 pages!)

             reply	other threads:[~2008-01-18 10:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-18 10:20 Michael Opdenacker [this message]
2008-01-18 16:34 ` [PATCH] Documentation: mention email-clients.txt in SubmittingPatches Randy Dunlap
2008-01-28 15:52   ` Paul Jackson
2008-01-28 16:17     ` Randy Dunlap
2008-01-28 19:32       ` Paul Jackson
2008-01-28 20:58         ` Randy Dunlap
2008-01-28 21:20           ` Randy Dunlap
2008-01-28 21:49             ` Paul Jackson
2008-01-28 21:48           ` Paul Jackson
2008-01-18 20:35 ` Jeff Garzik

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=200801181120.03168.michael-lists@free-electrons.com \
    --to=michael-lists@free-electrons.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    /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.