6 git-imap-send - Send a collection of patches from stdin to an IMAP folder
12 'git imap-send' [-v] [-q] [--[no-]curl]
17 This command uploads a mailbox generated with 'git format-patch'
18 into an IMAP drafts folder. This allows patches to be sent as
19 other email is when using mail clients that cannot read mailbox
20 files directly. The command also works with any general mailbox
21 in which emails have the fields "From", "Date", and "Subject" in
24 Typical usage is something like:
26 git format-patch --signoff --stdout --attach origin | git imap-send
41 Use libcurl to communicate with the IMAP server, unless tunneling
42 into it. Ignored if Git was built without the USE_CURL_FOR_IMAP_SEND
46 Talk to the IMAP server using git's own IMAP routines instead of
47 using libcurl. Ignored if Git was built with the NO_OPENSSL option
54 To use the tool, imap.folder and either imap.tunnel or imap.host must be set
55 to appropriate values.
60 include::config/imap.txt[]
67 ..........................
69 folder = "INBOX.Drafts"
70 tunnel = "ssh -q -C user@example.com /usr/bin/imapd ./Maildir 2> /dev/null"
71 ..........................
75 .........................
77 folder = "INBOX.Drafts"
78 host = imap://imap.example.com
81 .........................
83 Using direct mode with SSL:
85 .........................
87 folder = "INBOX.Drafts"
88 host = imaps://imap.example.com
93 .........................
98 To submit patches using GMail's IMAP interface, first, edit your ~/.gitconfig
99 to specify your account settings:
103 folder = "[Gmail]/Drafts"
104 host = imaps://imap.gmail.com
105 user = user@gmail.com
110 You might need to instead use: folder = "[Google Mail]/Drafts" if you get an error
111 that the "Folder doesn't exist".
113 Once the commits are ready to be sent, run the following command:
115 $ git format-patch --cover-letter -M --stdout origin/master | git imap-send
117 Just make sure to disable line wrapping in the email client (GMail's web
118 interface will wrap lines no matter what, so you need to use a real
123 It is still your responsibility to make sure that the email message
124 sent by your email program meets the standards of your project.
125 Many projects do not like patches to be attached. Some mail
126 agents will transform patches (e.g. wrap lines, send them as
127 format=flowed) in ways that make them fail. You will get angry
128 flames ridiculing you if you don't check this.
130 Thunderbird in particular is known to be problematic. Thunderbird
131 users may wish to visit this web page for more information:
132 http://kb.mozillazine.org/Plain_text_e-mail_-_Thunderbird#Completely_plain_email
136 linkgit:git-format-patch[1], linkgit:git-send-email[1], mbox(5)
140 Part of the linkgit:git[1] suite