|author||Tim Hockin <firstname.lastname@example.org>||2008-11-06 12:53:33 -0800|
|committer||Linus Torvalds <email@example.com>||2008-11-06 15:41:19 -0800|
Documentation/email-clients.txt: add some info about gmail
Signed-off-by: Tim Hockin <firstname.lastname@example.org> Signed-off-by: Andrew Morton <email@example.com> Signed-off-by: Linus Torvalds <firstname.lastname@example.org>
Diffstat (limited to 'Documentation/email-clients.txt')
1 files changed, 25 insertions, 0 deletions
diff --git a/Documentation/email-clients.txt b/Documentation/email-clients.txt
index 2ebb94d6ed8e..a618efab7b15 100644
@@ -213,4 +213,29 @@ TkRat (GUI)
Works. Use "Insert file..." or external editor.
+Gmail (Web GUI)
+If you just have to use Gmail to send patches, it CAN be made to work. It
+requires a bit of external help, though.
+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
+editor. There is a firefox extension called "ViewSourceWith"
+(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
+your favorite editor. When you want to send a patch, use this technique.
+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.