1git-send-email(1) 2================= 3 4NAME 5---- 6git-send-email - Send a collection of patches as emails 7 8 9SYNOPSIS 10-------- 11'git-send-email' [options] <file|directory> [... file|directory] 12 13 14 15DESCRIPTION 16----------- 17Takes the patches given on the command line and emails them out. 18 19The header of the email is configurable by command line options. If not 20specified on the command line, the user will be prompted with a ReadLine 21enabled interface to provide the necessary information. 22 23OPTIONS 24------- 25The options available are: 26 27--bcc:: 28 Specify a "Bcc:" value for each email. 29+ 30The --bcc option must be repeated for each user you want on the bcc list. 31 32--cc:: 33 Specify a starting "Cc:" value for each email. 34+ 35The --cc option must be repeated for each user you want on the cc list. 36 37--chain-reply-to, --no-chain-reply-to:: 38 If this is set, each email will be sent as a reply to the previous 39 email sent. If disabled with "--no-chain-reply-to", all emails after 40 the first will be sent as replies to the first email sent. When using 41 this, it is recommended that the first file given be an overview of the 42 entire patch series. 43 Default is the value of the 'sendemail.chainreplyto' configuration 44 value; if that is unspecified, default to --chain-reply-to. 45 46--compose:: 47 Use $EDITOR to edit an introductory message for the 48 patch series. 49 50--from:: 51 Specify the sender of the emails. This will default to 52 the value GIT_COMMITTER_IDENT, as returned by "git-var -l". 53 The user will still be prompted to confirm this entry. 54 55--in-reply-to:: 56 Specify the contents of the first In-Reply-To header. 57 Subsequent emails will refer to the previous email 58 instead of this if --chain-reply-to is set (the default) 59 Only necessary if --compose is also set. If --compose 60 is not set, this will be prompted for. 61 62--no-signed-off-by-cc:: 63 Do not add emails found in Signed-off-by: lines to the cc list. 64 65--quiet:: 66 Make git-send-email less verbose. One line per email should be 67 all that is output. 68 69--smtp-server:: 70 If set, specifies the outgoing SMTP server to use. A full 71 pathname of a sendmail-like program can be specified instead; 72 the program must support the `-i` option. Default value can 73 be specified by the 'sendemail.smtpserver' configuration 74 option; the built-in default is `/usr/sbin/sendmail` or 75 `/usr/lib/sendmail` if such program is available, or 76 `localhost` otherwise. 77 78--subject:: 79 Specify the initial subject of the email thread. 80 Only necessary if --compose is also set. If --compose 81 is not set, this will be prompted for. 82 83--suppress-from:: 84 Do not add the From: address to the cc: list, if it shows up in a From: 85 line. 86 87--to:: 88 Specify the primary recipient of the emails generated. 89 Generally, this will be the upstream maintainer of the 90 project involved. 91+ 92The --to option must be repeated for each user you want on the to list. 93 94 95CONFIGURATION 96------------- 97sendemail.aliasesfile:: 98 To avoid typing long email addresses, point this to one or more 99 email aliases files. You must also supply 'sendemail.aliasfiletype'. 100 101sendemail.aliasfiletype:: 102 Format of the file(s) specified in sendemail.aliasesfile. Must be 103 one of 'mutt', 'mailrc', 'pine', or 'gnus'. 104 105sendemail.bcc:: 106 Email address (or alias) to always bcc. 107 108sendemail.chainreplyto:: 109 Boolean value specifying the default to the '--chain_reply_to' 110 parameter. 111 112sendemail.smtpserver:: 113 Default smtp server to use. 114 115Author 116------ 117Written by Ryan Anderson <ryan@michonline.com> 118 119git-send-email is originally based upon 120send_lots_of_email.pl by Greg Kroah-Hartman. 121 122Documentation 123-------------- 124Documentation by Ryan Anderson 125 126GIT 127--- 128Part of the gitlink:git[7] suite 129