Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
- 220.127.116.11 → 18.104.22.168 no changes
- 22.214.171.124 08/24/11
- 126.96.36.199 → 1.7.6 no changes
- 188.8.131.52 05/26/11
- 184.108.40.206 → 220.127.116.11 no changes
- 1.7.5 04/24/11
- 18.104.22.168 → 22.214.171.124 no changes
- 1.7.1 04/24/10
- 126.96.36.199 → 188.8.131.52 no changes
- 184.108.40.206 04/11/10
- 220.127.116.11 → 18.104.22.168 no changes
- 1.7.0 02/12/10
- 22.214.171.124 → 126.96.36.199 no changes
- 1.6.3 05/07/09
- 188.8.131.52 no changes
- 184.108.40.206 04/20/09
- 220.127.116.11 → 18.104.22.168 no changes
- 1.6.2 03/04/09
- 22.214.171.124 → 126.96.36.199 no changes
- 1.6.1 12/25/08
git-imap-send(1) Manual Page
git-imap-send - Send a collection of patches from stdin to an IMAP folder
This command uploads a mailbox generated with git format-patch into an IMAP drafts folder. This allows patches to be sent as other email is when using mail clients that cannot read mailbox files directly. The command also works with any general mailbox in which emails have the fields "From", "Date", and "Subject" in that order.
Typical usage is something like:
git format-patch --signoff --stdout --attach origin | git imap-send
To use the tool, imap.folder and either imap.tunnel or imap.host must be set to appropriate values.
The folder to drop the mails into, which is typically the Drafts folder. For example: "INBOX.Drafts", "INBOX/Drafts" or "[Gmail]/Drafts". Required to use imap-send.
Command used to setup a tunnel to the IMAP server through which commands will be piped instead of using a direct network connection to the server. Required when imap.host is not set to use imap-send.
A URL identifying the server. Use a imap:// prefix for non-secure connections and a imaps:// prefix for secure connections. Ignored when imap.tunnel is set, but required to use imap-send otherwise.
The username to use when logging in to the server.
The password to use when logging in to the server.
An integer port number to connect to on the server. Defaults to 143 for imap:// hosts and 993 for imaps:// hosts. Ignored when imap.tunnel is set.
A boolean to enable/disable verification of the server certificate used by the SSL/TLS connection. Default is true. Ignored when imap.tunnel is set.
A boolean to enable/disable the use of html encoding when sending a patch. An html encoded patch will be bracketed with <pre> and have a content type of text/html. Ironically, enabling this option causes Thunderbird to send the patch as a plain/text, format=fixed email. Default is false.
Specify authenticate method for authentication with IMAP server. Current supported method is CRAM-MD5 only.
Using tunnel mode:
[imap] folder = "INBOX.Drafts" tunnel = "ssh -q -C firstname.lastname@example.org /usr/bin/imapd ./Maildir 2> /dev/null"
Using direct mode:
[imap] folder = "INBOX.Drafts" host = imap://imap.example.com user = bob pass = p4ssw0rd
Using direct mode with SSL:
[imap] folder = "INBOX.Drafts" host = imaps://imap.example.com user = bob pass = p4ssw0rd port = 123 sslverify = false
It is still your responsibility to make sure that the email message sent by your email program meets the standards of your project. Many projects do not like patches to be attached. Some mail agents will transform patches (e.g. wrap lines, send them as format=flowed) in ways that make them fail. You will get angry flames ridiculing you if you don't check this.
Thunderbird in particular is known to be problematic. Thunderbird users may wish to visit this web page for more information: http://kb.mozillazine.org/Plain_text_e-mail_-Thunderbird#Completelyplain_email
Part of the git(1) suite