Commit 5ce9f07b authored by Dave Young's avatar Dave Young Committed by Linus Torvalds

Documentation/email-clients.txt: update gmail information

Gmail web gui does not work for sending patches now even with firefox
"view source with" extension.  It will use windows style line breaks to
wrap lines automatically when sening email.

Rewrite the gmail web gui part of email client documentation.
Signed-off-by: default avatarDave Young <hidave.darkstar@gmail.com>
Cc: Randy Dunlap <rdunlap@xenotime.net>
Cc: Martin Bligh <mbligh@mbligh.org>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
parent 4c98ecaf
...@@ -216,26 +216,14 @@ Works. Use "Insert file..." or external editor. ...@@ -216,26 +216,14 @@ Works. Use "Insert file..." or external editor.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Gmail (Web GUI) Gmail (Web GUI)
If you just have to use Gmail to send patches, it CAN be made to work. It Does not work for sending patches.
requires a bit of external help, though.
Gmail web client converts tabs to spaces automatically.
The first problem is that Gmail converts tabs to spaces. This will
totally break your patches. To prevent this, you have to use a different At the same time it wraps lines every 78 chars with CRLF style line breaks
editor. There is a firefox extension called "ViewSourceWith" although tab2space problem can be solved with external editor.
(https://addons.mozilla.org/en-US/firefox/addon/394) which allows you to
edit any text box in the editor of your choice. Configure it to launch Another problem is that Gmail will base64-encode any message that has a
your favorite editor. When you want to send a patch, use this technique. non-ASCII character. That includes things like European names.
Once you have crafted your messsage + patch, save and exit the editor,
which should reload the Gmail edit box. GMAIL WILL PRESERVE THE TABS.
Hoorah. Apparently you can cut-n-paste literal tabs, but Gmail will
convert those to spaces upon sending!
The second problem is that Gmail converts tabs to spaces on replies. If
you reply to a patch, don't expect to be able to apply it as a patch.
The last problem is that Gmail will base64-encode any message that has a
non-ASCII character. That includes things like European names. Be aware.
Gmail is not convenient for lkml patches, but CAN be made to work.
### ###
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment