6 git-send-email - Send a collection of patches as emails
11 'git-send-email' [options] <file|directory> [... file|directory]
17 Takes the patches given on the command line and emails them out.
19 The header of the email is configurable by command line options. If not
20 specified on the command line, the user will be prompted with a ReadLine
21 enabled interface to provide the necessary information.
25 The options available are:
28 Specify a "Bcc:" value for each email.
30 The --bcc option must be repeated for each user you want on the bcc list.
33 Specify a starting "Cc:" value for each email.
35 The --cc option must be repeated for each user you want on the cc list.
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
43 Default is --chain-reply-to
46 Use $EDITOR to edit an introductory message for the
50 Specify the sender of the emails. This will default to
51 the value GIT_COMMITTER_IDENT, as returned by "git-var -l".
52 The user will still be prompted to confirm this entry.
55 Specify the contents of the first In-Reply-To header.
56 Subsequent emails will refer to the previous email
57 instead of this if --chain-reply-to is set (the default)
58 Only necessary if --compose is also set. If --compose
59 is not set, this will be prompted for.
61 --no-signed-off-by-cc::
62 Do not add emails found in Signed-off-by: lines to the cc list.
65 Make git-send-email less verbose. One line per email should be
69 If set, specifies the outgoing SMTP server to use. Defaults to
73 Specify the initial subject of the email thread.
74 Only necessary if --compose is also set. If --compose
75 is not set, this will be prompted for.
78 Do not add the From: address to the cc: list, if it shows up in a From:
82 Specify the primary recipient of the emails generated.
83 Generally, this will be the upstream maintainer of the
86 The --to option must be repeated for each user you want on the to list.
91 Written by Ryan Anderson <ryan@michonline.com>
93 git-send-email is originally based upon
94 send_lots_of_email.pl by Greg Kroah-Hartman.
98 Documentation by Ryan Anderson
102 Part of the gitlink:git[7] suite