@@ -376,9 +376,36 @@ Thunderbird
376
376
377
377
(A Large Angry SCM)
378
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
+
379
383
Here are some hints on how to successfully submit patches inline using
380
384
Thunderbird.
381
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
+
382
409
This recipe appears to work with the current [*1*] Thunderbird from Suse.
383
410
384
411
The following Thunderbird extensions are needed:
0 commit comments