{"thread":{"id":"17762","subject":"[PATCH v2] Update documentation to add further information about using Thunderbird with git-imap-send.","startedAt":"2009-02-12T21:17:04Z","lastAt":"2009-02-12T21:17:04Z","messageCount":1,"participants":["Jeremy White"],"isPatch":true,"patchVersion":2,"patchTotal":null},"messages":[{"id":"104425","messageId":"499491D0.5000908@codeweavers.com","threadId":"17762","inReplyTo":null,"subject":"[PATCH v2] Update documentation to add further information about using Thunderbird with git-imap-send.","fromName":"Jeremy White","fromEmail":"jwhite@codeweavers.com","sentAt":"2009-02-12T21:17:04Z","receivedAt":"2009-02-12T21:17:04Z","isPatch":true,"sender":{"key":"jwhite@codeweavers.com","avatar":"https://avatars.githubusercontent.com/u/1063742?v=4"},"body":"Signed-off-by: Jeremy White <jwhite@codeweavers.com>\n---\n\nWith thanks to Jakub Narebski, who caught that I had the boolean\nflag inverted.\n\n\n Documentation/SubmittingPatches |   27 +++++++++++++++++++++++++++\n Documentation/git-imap-send.txt |   14 ++++++++++++++\n 2 files changed, 41 insertions(+), 0 deletions(-)\n\ndiff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches\nindex ba07c8c..9b559ad 100644\n--- a/Documentation/SubmittingPatches\n+++ b/Documentation/SubmittingPatches\n@@ -376,9 +376,36 @@ Thunderbird\n \n (A Large Angry SCM)\n \n+By default, Thunderbird will both wrap emails as well as flag them as\n+being 'format=flowed', both of which will make the resulting email unusable\n+by git.\n+\n Here are some hints on how to successfully submit patches inline using\n Thunderbird.\n \n+There are two different approaches.  One approach is to configure\n+Thunderbird to not mangle patches.  The second approach is to use\n+an external editor to keep Thunderbird from mangling the patches.\n+\n+Approach #1 (configuration):\n+\n+This recipe is current as of Thunderbird 2.0.0.19.  Three steps:\n+  1.  Configure your mail server composition as plain text\n+      Edit...Account Settings...Composition & Addressing,\n+        uncheck 'Compose Messages in HTML'.\n+  2.  Configure your general composition window to not wrap\n+      Edit..Preferences..Composition, wrap plain text messages at 0\n+  3.  Disable the use of format=flowed\n+      Edit..Preferences..Advanced..Config Editor.  Search for:\n+        mailnews.send_plaintext_flowed\n+      toggle it to make sure it is set to 'false'.\n+\n+After that is done, you should be able to compose email as you\n+otherwise would (cut + paste, git-format-patch | git-imap-send, etc),\n+and the patches should not be mangled.\n+\n+Approach #2 (external editor):\n+\n This recipe appears to work with the current [*1*] Thunderbird from Suse.\n \n The following Thunderbird extensions are needed:\ndiff --git a/Documentation/git-imap-send.txt b/Documentation/git-imap-send.txt\nindex bd49a0a..1685f04 100644\n--- a/Documentation/git-imap-send.txt\n+++ b/Documentation/git-imap-send.txt\n@@ -98,6 +98,20 @@ Using direct mode with SSL:\n ..........................\n \n \n+CAUTION\n+-------\n+It is still your responsibility to make sure that the email message\n+sent by your email program meets the standards of your project.\n+Many projects do not like patches to be attached.  Some mail\n+agents will transform patches (e.g. wrap lines, send them as\n+format=flowed) in ways that make them fail.  You will get angry\n+flames ridiculing you if you don't check this.\n+\n+Thunderbird in particular is known to be problematic.  Thunderbird\n+users may wish to visit this web page for more information:\n+  http://kb.mozillazine.org/Plain_text_e-mail_-_Thunderbird#Completely_plain_email\n+\n+\n BUGS\n ----\n Doesn't handle lines starting with \"From \" in the message body.\n"}]}