Update documentation to add further information about using Thunderbird with git-imap-send.
Signed-off-by: Jeremy White <jwhite@codeweavers.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Jeremy White committed
Feb 12, 2009 at 15:17 UTC
1a526d483865d85aca3a10c650e85c44ad1f001b
2 files changed
+41
Documentation/SubmittingPatches
+27
@@ -376,9 +376,36 @@ Thunderbird
376
377
(A Large Angry SCM)
378
379
+By default, Thunderbird will both wrap emails as well as flag them as
380
+being 'format=flowed', both of which will make the resulting email unusable
381
+by git.
382
+
383
Here are some hints on how to successfully submit patches inline using
384
Thunderbird.
385
386
+There are two different approaches. One approach is to configure
387
+Thunderbird to not mangle patches. The second approach is to use
388
+an external editor to keep Thunderbird from mangling the patches.
389
+
390
+Approach #1 (configuration):
391
+
392
+This recipe is current as of Thunderbird 2.0.0.19. Three steps:
393
+ 1. Configure your mail server composition as plain text
394
+ Edit...Account Settings...Composition & Addressing,
395
+ uncheck 'Compose Messages in HTML'.
396
+ 2. Configure your general composition window to not wrap
397
+ Edit..Preferences..Composition, wrap plain text messages at 0
398
+ 3. Disable the use of format=flowed
399
+ Edit..Preferences..Advanced..Config Editor. Search for:
400
+ mailnews.send_plaintext_flowed
401
+ toggle it to make sure it is set to 'false'.
402
+
403
+After that is done, you should be able to compose email as you
404
+otherwise would (cut + paste, git-format-patch | git-imap-send, etc),
405
+and the patches should not be mangled.
406
+
407
+Approach #2 (external editor):
408
+
409
This recipe appears to work with the current [*1*] Thunderbird from Suse.
410
411
The following Thunderbird extensions are needed:
Documentation/git-imap-send.txt
+14
@@ -98,6 +98,20 @@ Using direct mode with SSL:
98
..........................
99
100
101
+CAUTION
102
+-------
103
+It is still your responsibility to make sure that the email message
104
+sent by your email program meets the standards of your project.
105
+Many projects do not like patches to be attached. Some mail
106
+agents will transform patches (e.g. wrap lines, send them as
107
+format=flowed) in ways that make them fail. You will get angry
108
+flames ridiculing you if you don't check this.
109
+
110
+Thunderbird in particular is known to be problematic. Thunderbird
111
+users may wish to visit this web page for more information:
112
+ http://kb.mozillazine.org/Plain_text_e-mail_-_Thunderbird#Completely_plain_email
113
+
114
+
115
BUGS
116
----
117
Doesn't handle lines starting with "From " in the message body.