[lkml]   [2008]   [Nov]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Patch in this message
SubjectRe: [PATCH] SAM9 watchdog - supported on all SAM9 and CAP9 processors
On Wed, 5 Nov 2008 22:58:45 +0200
"Andrew Victor" <> wrote:

> > sylpheed mucks that up. text/plain attachments would be preferred,
> > please. Inlined non-wordwrapped, non-tab-replaced, non-space-stuffed
> > text would of course be even better.
> Unfortunately, gmail seems to mess up (ie, corrupt the whitespace of)
> the inlined patches.

trust me, I noticed ;)

I have this queued:

From: Tim Hockin <>

Signed-off-by: Tim Hockin <>
Signed-off-by: Andrew Morton <>

Documentation/email-clients.txt | 25 +++++++++++++++++++++++++
1 file changed, 25 insertions(+)

diff -puN Documentation/email-clients.txt~documentation-email-clientstxt-add-some-info-about-gmail Documentation/email-clients.txt
--- a/Documentation/email-clients.txt~documentation-email-clientstxt-add-some-info-about-gmail
+++ a/Documentation/email-clients.txt
@@ -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"
+( 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.

 \ /
  Last update: 2008-11-05 22:17    [W:0.034 / U:5.316 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site