diff options
-rw-r--r-- | Documentation/email-clients.txt | 25 |
1 files changed, 25 insertions, 0 deletions
diff --git a/Documentation/email-clients.txt b/Documentation/email-clients.txt index 2ebb94d6ed8e..a618efab7b15 100644 --- a/Documentation/email-clients.txt +++ b/Documentation/email-clients.txt | |||
@@ -213,4 +213,29 @@ TkRat (GUI) | |||
213 | 213 | ||
214 | Works. Use "Insert file..." or external editor. | 214 | Works. Use "Insert file..." or external editor. |
215 | 215 | ||
216 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ||
217 | Gmail (Web GUI) | ||
218 | |||
219 | If you just have to use Gmail to send patches, it CAN be made to work. It | ||
220 | requires a bit of external help, though. | ||
221 | |||
222 | The first problem is that Gmail converts tabs to spaces. This will | ||
223 | totally break your patches. To prevent this, you have to use a different | ||
224 | editor. There is a firefox extension called "ViewSourceWith" | ||
225 | (https://addons.mozilla.org/en-US/firefox/addon/394) which allows you to | ||
226 | edit any text box in the editor of your choice. Configure it to launch | ||
227 | your favorite editor. When you want to send a patch, use this technique. | ||
228 | Once you have crafted your messsage + patch, save and exit the editor, | ||
229 | which should reload the Gmail edit box. GMAIL WILL PRESERVE THE TABS. | ||
230 | Hoorah. Apparently you can cut-n-paste literal tabs, but Gmail will | ||
231 | convert those to spaces upon sending! | ||
232 | |||
233 | The second problem is that Gmail converts tabs to spaces on replies. If | ||
234 | you reply to a patch, don't expect to be able to apply it as a patch. | ||
235 | |||
236 | The last problem is that Gmail will base64-encode any message that has a | ||
237 | non-ASCII character. That includes things like European names. Be aware. | ||
238 | |||
239 | Gmail is not convenient for lkml patches, but CAN be made to work. | ||
240 | |||
216 | ### | 241 | ### |