6 git-send-email - Send a collection of patches as emails
11 'git send-email' [options] <file|directory|rev-list options>...
16 Takes the patches given on the command line and emails them out.
17 Patches can be specified as files, directories (which will send all
18 files in the directory), or directly as a revision list. In the
19 last case, any format accepted by linkgit:git-format-patch[1] can
20 be passed to git send-email.
22 The header of the email is configurable by command line options. If not
23 specified on the command line, the user will be prompted with a ReadLine
24 enabled interface to provide the necessary information.
26 There are two formats accepted for patch files:
30 This is what linkgit:git-format-patch[1] generates. Most headers and MIME
31 formatting are ignored.
33 2. The original format used by Greg Kroah-Hartman's 'send_lots_of_email.pl'
36 This format expects the first line of the file to contain the "Cc:" value
37 and the "Subject:" of the message as the second line.
47 Review and edit each patch you're about to send. See the
48 CONFIGURATION section for 'sendemail.multiedit'.
51 Specify a "Bcc:" value for each email. Default is the value of
54 The --bcc option must be repeated for each user you want on the bcc list.
57 Specify a starting "Cc:" value for each email.
58 Default is the value of 'sendemail.cc'.
60 The --cc option must be repeated for each user you want on the cc list.
63 Use $GIT_EDITOR, core.editor, $VISUAL, or $EDITOR to edit an
64 introductory message for the patch series.
66 When '--compose' is used, git send-email will use the From, Subject, and
67 In-Reply-To headers specified in the message. If the body of the message
68 (what you type after the headers and a blank line) only contains blank
69 (or GIT: prefixed) lines the summary won't be sent, but From, Subject,
70 and In-Reply-To headers will be used unless they are removed.
72 Missing From or In-Reply-To headers will be prompted for.
74 See the CONFIGURATION section for 'sendemail.multiedit'.
77 Specify the sender of the emails. If not specified on the command line,
78 the value of the 'sendemail.from' configuration option is used. If
79 neither the command line option nor 'sendemail.from' are set, then the
80 user will be prompted for the value. The default for the prompt will be
81 the value of GIT_AUTHOR_IDENT, or GIT_COMMITTER_IDENT if that is not
82 set, as returned by "git var -l".
84 --in-reply-to=<identifier>::
85 Specify the contents of the first In-Reply-To header.
86 Subsequent emails will refer to the previous email
87 instead of this if --chain-reply-to is set (the default)
88 Only necessary if --compose is also set. If --compose
89 is not set, this will be prompted for.
92 Specify the initial subject of the email thread.
93 Only necessary if --compose is also set. If --compose
94 is not set, this will be prompted for.
97 Specify the primary recipient of the emails generated. Generally, this
98 will be the upstream maintainer of the project involved. Default is the
99 value of the 'sendemail.to' configuration value; if that is unspecified,
100 this will be prompted for.
102 The --to option must be repeated for each user you want on the to list.
108 --envelope-sender=<address>::
109 Specify the envelope sender used to send the emails.
110 This is useful if your default address is not the address that is
111 subscribed to a list. If you use the sendmail binary, you must have
112 suitable privileges for the -f parameter. Default is the value of
113 the 'sendemail.envelopesender' configuration variable; if that is
114 unspecified, choosing the envelope sender is left to your MTA.
116 --smtp-encryption=<encryption>::
117 Specify the encryption to use, either 'ssl' or 'tls'. Any other
118 value reverts to plain SMTP. Default is the value of
119 'sendemail.smtpencryption'.
121 --smtp-pass[=<password>]::
122 Password for SMTP-AUTH. The argument is optional: If no
123 argument is specified, then the empty string is used as
124 the password. Default is the value of 'sendemail.smtppass',
125 however '--smtp-pass' always overrides this value.
127 Furthermore, passwords need not be specified in configuration files
128 or on the command line. If a username has been specified (with
129 '--smtp-user' or a 'sendemail.smtpuser'), but no password has been
130 specified (with '--smtp-pass' or 'sendemail.smtppass'), then the
131 user is prompted for a password while the input is masked for privacy.
133 --smtp-server=<host>::
134 If set, specifies the outgoing SMTP server to use (e.g.
135 `smtp.example.com` or a raw IP address). Alternatively it can
136 specify a full pathname of a sendmail-like program instead;
137 the program must support the `-i` option. Default value can
138 be specified by the 'sendemail.smtpserver' configuration
139 option; the built-in default is `/usr/sbin/sendmail` or
140 `/usr/lib/sendmail` if such program is available, or
141 `localhost` otherwise.
143 --smtp-server-port=<port>::
144 Specifies a port different from the default port (SMTP
145 servers typically listen to smtp port 25 and ssmtp port
146 465); symbolic port names (e.g. "submission" instead of 465)
147 are also accepted. The port can also be set with the
148 'sendemail.smtpserverport' configuration variable.
151 Legacy alias for '--smtp-encryption ssl'.
154 Username for SMTP-AUTH. Default is the value of 'sendemail.smtpuser';
155 if a username is not specified (with '--smtp-user' or 'sendemail.smtpuser'),
156 then authentication is not attempted.
163 Specify a command to execute once per patch file which
164 should generate patch file specific "Cc:" entries.
165 Output of this command must be single email address per line.
166 Default is the value of 'sendemail.cccmd' configuration value.
168 --[no-]chain-reply-to::
169 If this is set, each email will be sent as a reply to the previous
170 email sent. If disabled with "--no-chain-reply-to", all emails after
171 the first will be sent as replies to the first email sent. When using
172 this, it is recommended that the first file given be an overview of the
173 entire patch series. Default is the value of the 'sendemail.chainreplyto'
174 configuration value; if that is unspecified, default to --chain-reply-to.
176 --identity=<identity>::
177 A configuration identity. When given, causes values in the
178 'sendemail.<identity>' subsection to take precedence over
179 values in the 'sendemail' section. The default identity is
180 the value of 'sendemail.identity'.
182 --[no-]signed-off-by-cc::
183 If this is set, add emails found in Signed-off-by: or Cc: lines to the
184 cc list. Default is the value of 'sendemail.signedoffbycc' configuration
185 value; if that is unspecified, default to --signed-off-by-cc.
187 --suppress-cc=<category>::
188 Specify an additional category of recipients to suppress the
192 - 'author' will avoid including the patch author
193 - 'self' will avoid including the sender
194 - 'cc' will avoid including anyone mentioned in Cc lines in the patch header
195 except for self (use 'self' for that).
196 - 'bodycc' will avoid including anyone mentioned in Cc lines in the
197 patch body (commit message) except for self (use 'self' for that).
198 - 'sob' will avoid including anyone mentioned in Signed-off-by lines except
199 for self (use 'self' for that).
200 - 'cccmd' will avoid running the --cc-cmd.
201 - 'body' is equivalent to 'sob' + 'bodycc'
202 - 'all' will suppress all auto cc values.
205 Default is the value of 'sendemail.suppresscc' configuration value; if
206 that is unspecified, default to 'self' if --suppress-from is
207 specified, as well as 'body' if --no-signed-off-cc is specified.
209 --[no-]suppress-from::
210 If this is set, do not add the From: address to the cc: list.
211 Default is the value of 'sendemail.suppressfrom' configuration
212 value; if that is unspecified, default to --no-suppress-from.
215 If this is set, the In-Reply-To header will be set on each email sent.
216 If disabled with "--no-thread", no emails will have the In-Reply-To
217 header set, unless specified with --in-reply-to.
218 Default is the value of the 'sendemail.thread' configuration
219 value; if that is unspecified, default to --thread.
226 Confirm just before sending:
229 - 'always' will always confirm before sending
230 - 'never' will never confirm before sending
231 - 'cc' will confirm before sending when send-email has automatically
232 added addresses from the patch to the Cc list
233 - 'compose' will confirm before sending the first message when using --compose.
234 - 'auto' is equivalent to 'cc' + 'compose'
237 Default is the value of 'sendemail.confirm' configuration value; if that
238 is unspecified, default to 'auto' unless any of the suppress options
239 have been specified, in which case default to 'compose'.
242 Do everything except actually send the emails.
244 --[no-]format-patch::
245 When an argument may be understood either as a reference or as a file name,
246 choose to understand it as a format-patch argument ('--format-patch')
247 or as a file name ('--no-format-patch'). By default, when such a conflict
248 occurs, git send-email will fail.
251 Make git-send-email less verbose. One line per email should be
255 Perform sanity checks on patches.
256 Currently, validation means the following:
259 * Warn of patches that contain lines longer than 998 characters; this
260 is due to SMTP limits as described by http://www.ietf.org/rfc/rfc2821.txt.
263 Default is the value of 'sendemail.validate'; if this is not set,
264 default to '--validate'.
270 sendemail.aliasesfile::
271 To avoid typing long email addresses, point this to one or more
272 email aliases files. You must also supply 'sendemail.aliasfiletype'.
274 sendemail.aliasfiletype::
275 Format of the file(s) specified in sendemail.aliasesfile. Must be
276 one of 'mutt', 'mailrc', 'pine', 'elm', or 'gnus'.
278 sendemail.multiedit::
279 If true (default), a single editor instance will be spawned to edit
280 files you have to edit (patches when '--annotate' is used, and the
281 summary when '--compose' is used). If false, files will be edited one
282 after the other, spawning a new editor each time.
285 Sets the default for whether to confirm before sending. Must be
286 one of 'always', 'never', 'cc', 'compose', or 'auto'. See '--confirm'
287 in the previous section for the meaning of these values.
292 Written by Ryan Anderson <ryan@michonline.com>
294 git-send-email is originally based upon
295 send_lots_of_email.pl by Greg Kroah-Hartman.
300 Documentation by Ryan Anderson
305 Part of the linkgit:git[1] suite