Commit 097091c0a83754f426b3d0b22afa6c984752dbf7

Authored by Michael Opdenacker
Committed by Adrian Bunk
1 parent 09c6dd3c9d

Documentation: mention email-clients.txt in SubmittingPatches

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.

Signed-off-by: Michael Opdenacker <michael@free-electrons.com>
Acked-by: Randy Dunlap <randy.dunlap@oracle.com>
Acked-by: Jeff Garzik <jeff@garzik.org>
Signed-off-by: Adrian Bunk <bunk@kernel.org>

Showing 1 changed file with 2 additions and 14 deletions Side-by-side Diff

Documentation/SubmittingPatches
... ... @@ -220,20 +220,8 @@
220 220 Exception: If your mailer is mangling patches then someone may ask
221 221 you to re-send them using MIME.
222 222  
223   -
224   -WARNING: Some mailers like Mozilla send your messages with
225   ----- message header ----
226   -Content-Type: text/plain; charset=us-ascii; format=flowed
227   ----- message header ----
228   -The problem is that "format=flowed" makes some of the mailers
229   -on receiving side to replace TABs with spaces and do similar
230   -changes. Thus the patches from you can look corrupted.
231   -
232   -To fix this just make your mozilla defaults/pref/mailnews.js file to look like:
233   -pref("mailnews.send_plaintext_flowed", false); // RFC 2646=======
234   -pref("mailnews.display.disable_format_flowed_support", true);
235   -
236   -
  223 +See Documentation/email-clients.txt for hints about configuring
  224 +your e-mail client so that it sends your patches untouched.
237 225  
238 226 8) E-mail size.
239 227