'\" t
.\" Title: git-send-email
.\" Author: [FIXME: author] [see http://docbook.sf.net/el/author]
.\" Generator: DocBook XSL Stylesheets v1.76.1
.\" 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] \&...
.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=
.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=
.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=
.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=
.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=
.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=
.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=
.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 \&. 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=
.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=
.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=
.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[=]
.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=
.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=
.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=