'\" t
.\"     Title: git-send-email
.\"    Author: [FIXME: author] [see http://docbook.sf.net/el/author]
.\" Generator: DocBook XSL Stylesheets v1.76.1 <http://docbook.sf.net/>
.\"      Date: 03/19/2016
.\"    Manual: Git Manual
.\"    Source: Git 1.7.10.4
.\"  Language: English
.\"
.TH "GIT\-SEND\-EMAIL" "1" "03/19/2016" "Git 1\&.7\&.10\&.4" "Git Manual"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.\" http://bugs.debian.org/507673
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\" -----------------------------------------------------------------
.\" * set default formatting
.\" -----------------------------------------------------------------
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
.SH "NAME"
git-send-email \- Send a collection of patches as emails
.SH "SYNOPSIS"
.sp
.nf
\fIgit send\-email\fR [options] <file|directory|rev\-list options>\&...
.fi
.sp
.SH "DESCRIPTION"
.sp
Takes the patches given on the command line and emails them out\&. Patches can be specified as files, directories (which will send all files in the directory), or directly as a revision list\&. In the last case, any format accepted by \fBgit-format-patch\fR(1) can be passed to git send\-email\&.
.sp
The header of the email is configurable by command line options\&. If not specified on the command line, the user will be prompted with a ReadLine enabled interface to provide the necessary information\&.
.sp
There are two formats accepted for patch files:
.sp
.RS 4
.ie n \{\
\h'-04' 1.\h'+01'\c
.\}
.el \{\
.sp -1
.IP "  1." 4.2
.\}
mbox format files
.sp
This is what
\fBgit-format-patch\fR(1)
generates\&. Most headers and MIME formatting are ignored\&.
.RE
.sp
.RS 4
.ie n \{\
\h'-04' 2.\h'+01'\c
.\}
.el \{\
.sp -1
.IP "  2." 4.2
.\}
The original format used by Greg Kroah\-Hartman\(cqs
\fIsend_lots_of_email\&.pl\fR
script
.sp
This format expects the first line of the file to contain the "Cc:" value and the "Subject:" of the message as the second line\&.
.RE
.SH "OPTIONS"
.SS "Composing"
.PP
\-\-annotate
.RS 4
Review and edit each patch you\(cqre about to send\&. See the CONFIGURATION section for
\fIsendemail\&.multiedit\fR\&.
.RE
.PP
\-\-bcc=<address>
.RS 4
Specify a "Bcc:" value for each email\&. Default is the value of
\fIsendemail\&.bcc\fR\&.
.sp
The \-\-bcc option must be repeated for each user you want on the bcc list\&.
.RE
.PP
\-\-cc=<address>
.RS 4
Specify a starting "Cc:" value for each email\&. Default is the value of
\fIsendemail\&.cc\fR\&.
.sp
The \-\-cc option must be repeated for each user you want on the cc list\&.
.RE
.PP
\-\-compose
.RS 4
Invoke a text editor (see GIT_EDITOR in
\fBgit-var\fR(1)) to edit an introductory message for the patch series\&.
.sp
When
\fI\-\-compose\fR
is used, git send\-email will use the From, Subject, and In\-Reply\-To headers specified in the message\&. If the body of the message (what you type after the headers and a blank line) only contains blank (or GIT: prefixed) lines the summary won\(cqt be sent, but From, Subject, and In\-Reply\-To headers will be used unless they are removed\&.
.sp
Missing From or In\-Reply\-To headers will be prompted for\&.
.sp
See the CONFIGURATION section for
\fIsendemail\&.multiedit\fR\&.
.RE
.PP
\-\-from=<address>
.RS 4
Specify the sender of the emails\&. If not specified on the command line, the value of the
\fIsendemail\&.from\fR
configuration option is used\&. If neither the command line option nor
\fIsendemail\&.from\fR
are set, then the user will be prompted for the value\&. The default for the prompt will be the value of GIT_AUTHOR_IDENT, or GIT_COMMITTER_IDENT if that is not set, as returned by "git var \-l"\&.
.RE
.PP
\-\-in\-reply\-to=<identifier>
.RS 4
Make the first mail (or all the mails with
\-\-no\-thread) appear as a reply to the given Message\-Id, which avoids breaking threads to provide a new patch series\&. The second and subsequent emails will be sent as replies according to the
\-\-[no]\-chain\-reply\-to
setting\&.
.sp
So for example when
\-\-thread
and
\-\-no\-chain\-reply\-to
are specified, the second and subsequent patches will be replies to the first one like in the illustration below where
[PATCH v2 0/3]
is in reply to
[PATCH 0/2]:
.sp
.if n \{\
.RS 4
.\}
.nf
[PATCH 0/2] Here is what I did\&.\&.\&.
  [PATCH 1/2] Clean up and tests
  [PATCH 2/2] Implementation
  [PATCH v2 0/3] Here is a reroll
    [PATCH v2 1/3] Clean up
    [PATCH v2 2/3] New tests
    [PATCH v2 3/3] Implementation
.fi
.if n \{\
.RE
.\}
.sp
Only necessary if \-\-compose is also set\&. If \-\-compose is not set, this will be prompted for\&.
.RE
.PP
\-\-subject=<string>
.RS 4
Specify the initial subject of the email thread\&. Only necessary if \-\-compose is also set\&. If \-\-compose is not set, this will be prompted for\&.
.RE
.PP
\-\-to=<address>
.RS 4
Specify the primary recipient of the emails generated\&. Generally, this will be the upstream maintainer of the project involved\&. Default is the value of the
\fIsendemail\&.to\fR
configuration value; if that is unspecified, and \-\-to\-cmd is not specified, this will be prompted for\&.
.sp
The \-\-to option must be repeated for each user you want on the to list\&.
.RE
.PP
\-\-8bit\-encoding=<encoding>
.RS 4
When encountering a non\-ASCII message or subject that does not declare its encoding, add headers/quoting to indicate it is encoded in <encoding>\&. Default is the value of the
\fIsendemail\&.assume8bitEncoding\fR; if that is unspecified, this will be prompted for if any non\-ASCII files are encountered\&.
.sp
Note that no attempts whatsoever are made to validate the encoding\&.
.RE
.SS "Sending"
.PP
\-\-envelope\-sender=<address>
.RS 4
Specify the envelope sender used to send the emails\&. This is useful if your default address is not the address that is subscribed to a list\&. In order to use the
\fIFrom\fR
address, set the value to "auto"\&. If you use the sendmail binary, you must have suitable privileges for the \-f parameter\&. Default is the value of the
\fIsendemail\&.envelopesender\fR
configuration variable; if that is unspecified, choosing the envelope sender is left to your MTA\&.
.RE
.PP
\-\-smtp\-encryption=<encryption>
.RS 4
Specify the encryption to use, either
\fIssl\fR
or
\fItls\fR\&. Any other value reverts to plain SMTP\&. Default is the value of
\fIsendemail\&.smtpencryption\fR\&.
.RE
.PP
\-\-smtp\-domain=<FQDN>
.RS 4
Specifies the Fully Qualified Domain Name (FQDN) used in the HELO/EHLO command to the SMTP server\&. Some servers require the FQDN to match your IP address\&. If not set, git send\-email attempts to determine your FQDN automatically\&. Default is the value of
\fIsendemail\&.smtpdomain\fR\&.
.RE
.PP
\-\-smtp\-pass[=<password>]
.RS 4
Password for SMTP\-AUTH\&. The argument is optional: If no argument is specified, then the empty string is used as the password\&. Default is the value of
\fIsendemail\&.smtppass\fR, however
\fI\-\-smtp\-pass\fR
always overrides this value\&.
.sp
Furthermore, passwords need not be specified in configuration files or on the command line\&. If a username has been specified (with
\fI\-\-smtp\-user\fR
or a
\fIsendemail\&.smtpuser\fR), but no password has been specified (with
\fI\-\-smtp\-pass\fR
or
\fIsendemail\&.smtppass\fR), then the user is prompted for a password while the input is masked for privacy\&.
.RE
.PP
\-\-smtp\-server=<host>
.RS 4
If set, specifies the outgoing SMTP server to use (e\&.g\&.
smtp\&.example\&.com
or a raw IP address)\&. Alternatively it can specify a full pathname of a sendmail\-like program instead; the program must support the
\-i
option\&. Default value can be specified by the
\fIsendemail\&.smtpserver\fR
configuration option; the built\-in default is
/usr/sbin/sendmail
or
/usr/lib/sendmail
if such program is available, or
localhost
otherwise\&.
.RE
.PP
\-\-smtp\-server\-port=<port>
.RS 4
Specifies a port different from the default port (SMTP servers typically listen to smtp port 25, but may also listen to submission port 587, or the common SSL smtp port 465); symbolic port names (e\&.g\&. "submission" instead of 587) are also accepted\&. The port can also be set with the
\fIsendemail\&.smtpserverport\fR
configuration variable\&.
.RE
.PP
\-\-smtp\-server\-option=<option>
.RS 4
If set, specifies the outgoing SMTP server option to use\&. Default value can be specified by the
\fIsendemail\&.smtpserveroption\fR
configuration option\&.
.sp
The \-\-smtp\-server\-option option must be repeated for each option you want to pass to the server\&. Likewise, different lines in the configuration files must be used for each option\&.
.RE
.PP
\-\-smtp\-ssl
.RS 4
Legacy alias for
\fI\-\-smtp\-encryption ssl\fR\&.
.RE
.PP
\-\-smtp\-user=<user>
.RS 4
Username for SMTP\-AUTH\&. Default is the value of
\fIsendemail\&.smtpuser\fR; if a username is not specified (with
\fI\-\-smtp\-user\fR
or
\fIsendemail\&.smtpuser\fR), then authentication is not attempted\&.
.RE
.PP
\-\-smtp\-debug=0|1
.RS 4
Enable (1) or disable (0) debug output\&. If enabled, SMTP commands and replies will be printed\&. Useful to debug TLS connection and authentication problems\&.
.RE
.SS "Automating"
.PP
\-\-to\-cmd=<command>
.RS 4
Specify a command to execute once per patch file which should generate patch file specific "To:" entries\&. Output of this command must be single email address per line\&. Default is the value of
\fIsendemail\&.tocmd\fR
configuration value\&.
.RE
.PP
\-\-cc\-cmd=<command>
.RS 4
Specify a command to execute once per patch file which should generate patch file specific "Cc:" entries\&. Output of this command must be single email address per line\&. Default is the value of
\fIsendemail\&.cccmd\fR
configuration value\&.
.RE
.PP
\-\-[no\-]chain\-reply\-to
.RS 4
If this is set, each email will be sent as a reply to the previous email sent\&. If disabled with "\-\-no\-chain\-reply\-to", all emails after the first will be sent as replies to the first email sent\&. When using this, it is recommended that the first file given be an overview of the entire patch series\&. Disabled by default, but the
\fIsendemail\&.chainreplyto\fR
configuration variable can be used to enable it\&.
.RE
.PP
\-\-identity=<identity>
.RS 4
A configuration identity\&. When given, causes values in the
\fIsendemail\&.<identity>\fR
subsection to take precedence over values in the
\fIsendemail\fR
section\&. The default identity is the value of
\fIsendemail\&.identity\fR\&.
.RE
.PP
\-\-[no\-]signed\-off\-by\-cc
.RS 4
If this is set, add emails found in Signed\-off\-by: or Cc: lines to the cc list\&. Default is the value of
\fIsendemail\&.signedoffbycc\fR
configuration value; if that is unspecified, default to \-\-signed\-off\-by\-cc\&.
.RE
.PP
\-\-suppress\-cc=<category>
.RS 4
Specify an additional category of recipients to suppress the auto\-cc of:
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}

\fIauthor\fR
will avoid including the patch author
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}

\fIself\fR
will avoid including the sender
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}

\fIcc\fR
will avoid including anyone mentioned in Cc lines in the patch header except for self (use
\fIself\fR
for that)\&.
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}

\fIbodycc\fR
will avoid including anyone mentioned in Cc lines in the patch body (commit message) except for self (use
\fIself\fR
for that)\&.
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}

\fIsob\fR
will avoid including anyone mentioned in Signed\-off\-by lines except for self (use
\fIself\fR
for that)\&.
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}

\fIcccmd\fR
will avoid running the \-\-cc\-cmd\&.
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}

\fIbody\fR
is equivalent to
\fIsob\fR
+
\fIbodycc\fR
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}

\fIall\fR
will suppress all auto cc values\&.
.RE
.sp
Default is the value of
\fIsendemail\&.suppresscc\fR
configuration value; if that is unspecified, default to
\fIself\fR
if \-\-suppress\-from is specified, as well as
\fIbody\fR
if \-\-no\-signed\-off\-cc is specified\&.
.RE
.PP
\-\-[no\-]suppress\-from
.RS 4
If this is set, do not add the From: address to the cc: list\&. Default is the value of
\fIsendemail\&.suppressfrom\fR
configuration value; if that is unspecified, default to \-\-no\-suppress\-from\&.
.RE
.PP
\-\-[no\-]thread
.RS 4
If this is set, the In\-Reply\-To and References headers will be added to each email sent\&. Whether each mail refers to the previous email (deep
threading per
\fIgit format\-patch\fR
wording) or to the first email (shallow
threading) is governed by "\-\-[no\-]chain\-reply\-to"\&.
.sp
If disabled with "\-\-no\-thread", those headers will not be added (unless specified with \-\-in\-reply\-to)\&. Default is the value of the
\fIsendemail\&.thread\fR
configuration value; if that is unspecified, default to \-\-thread\&.
.sp
It is up to the user to ensure that no In\-Reply\-To header already exists when
\fIgit send\-email\fR
is asked to add it (especially note that
\fIgit format\-patch\fR
can be configured to do the threading itself)\&. Failure to do so may not produce the expected result in the recipient\(cqs MUA\&.
.RE
.SS "Administering"
.PP
\-\-confirm=<mode>
.RS 4
Confirm just before sending:
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}

\fIalways\fR
will always confirm before sending
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}

\fInever\fR
will never confirm before sending
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}

\fIcc\fR
will confirm before sending when send\-email has automatically added addresses from the patch to the Cc list
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}

\fIcompose\fR
will confirm before sending the first message when using \-\-compose\&.
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}

\fIauto\fR
is equivalent to
\fIcc\fR
+
\fIcompose\fR
.RE
.sp
Default is the value of
\fIsendemail\&.confirm\fR
configuration value; if that is unspecified, default to
\fIauto\fR
unless any of the suppress options have been specified, in which case default to
\fIcompose\fR\&.
.RE
.PP
\-\-dry\-run
.RS 4
Do everything except actually send the emails\&.
.RE
.PP
\-\-[no\-]format\-patch
.RS 4
When an argument may be understood either as a reference or as a file name, choose to understand it as a format\-patch argument (\fI\-\-format\-patch\fR) or as a file name (\fI\-\-no\-format\-patch\fR)\&. By default, when such a conflict occurs, git send\-email will fail\&.
.RE
.PP
\-\-quiet
.RS 4
Make git\-send\-email less verbose\&. One line per email should be all that is output\&.
.RE
.PP
\-\-[no\-]validate
.RS 4
Perform sanity checks on patches\&. Currently, validation means the following:
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
Warn of patches that contain lines longer than 998 characters; this is due to SMTP limits as described by
\m[blue]\fBhttp://www\&.ietf\&.org/rfc/rfc2821\&.txt\fR\m[]\&.
.RE
.sp
Default is the value of
\fIsendemail\&.validate\fR; if this is not set, default to
\fI\-\-validate\fR\&.
.RE
.PP
\-\-force
.RS 4
Send emails even if safety checks would prevent it\&.
.RE
.SH "CONFIGURATION"
.PP
sendemail\&.aliasesfile
.RS 4
To avoid typing long email addresses, point this to one or more email aliases files\&. You must also supply
\fIsendemail\&.aliasfiletype\fR\&.
.RE
.PP
sendemail\&.aliasfiletype
.RS 4
Format of the file(s) specified in sendemail\&.aliasesfile\&. Must be one of
\fImutt\fR,
\fImailrc\fR,
\fIpine\fR,
\fIelm\fR, or
\fIgnus\fR\&.
.RE
.PP
sendemail\&.multiedit
.RS 4
If true (default), a single editor instance will be spawned to edit files you have to edit (patches when
\fI\-\-annotate\fR
is used, and the summary when
\fI\-\-compose\fR
is used)\&. If false, files will be edited one after the other, spawning a new editor each time\&.
.RE
.PP
sendemail\&.confirm
.RS 4
Sets the default for whether to confirm before sending\&. Must be one of
\fIalways\fR,
\fInever\fR,
\fIcc\fR,
\fIcompose\fR, or
\fIauto\fR\&. See
\fI\-\-confirm\fR
in the previous section for the meaning of these values\&.
.RE
.SH "EXAMPLE"
.SS "Use gmail as the smtp server"
.sp
To use \fIgit send\-email\fR to send your patches through the GMail SMTP server, edit ~/\&.gitconfig to specify your account settings:
.sp
.if n \{\
.RS 4
.\}
.nf
[sendemail]
        smtpencryption = tls
        smtpserver = smtp\&.gmail\&.com
        smtpuser = yourname@gmail\&.com
        smtpserverport = 587
.fi
.if n \{\
.RE
.\}
.sp
Once your commits are ready to be sent to the mailing list, run the following commands:
.sp
.if n \{\
.RS 4
.\}
.nf
$ git format\-patch \-\-cover\-letter \-M origin/master \-o outgoing/
$ edit outgoing/0000\-*
$ git send\-email outgoing/*
.fi
.if n \{\
.RE
.\}
.sp
Note: the following perl modules are required Net::SMTP::SSL, MIME::Base64 and Authen::SASL
.SH "SEE ALSO"
.sp
\fBgit-format-patch\fR(1), \fBgit-imap-send\fR(1), mbox(5)
.SH "GIT"
.sp
Part of the \fBgit\fR(1) suite